Skip to content跳至正文
Harry Xin
Projects项目索引09
ctxtax05 / 09
← All work← 全部项目CONTEXT BUDGETING上下文预算

$ ctxtax

ctxtax

Before the prompt,
there is a cost.
还没开始提问,
上下文已经有了开销。

See how much context your MCP tool definitions take, where that budget goes, and which descriptions deserve a closer look.看清 MCP 工具定义占用多少上下文、预算花在哪里,以及哪些描述值得精简。

Open on GitHub在 GitHub 打开Explore ↓往下看 ↓
No mystery charges.
Read the definitions.
不猜开销,
先读工具定义。
CONTEXT / TAXRECEIPT 001
CTX / BUDGET RECEIPTEXAMPLE
ctxtax
Tool definitions工具定义占用
4,000 / 8,000
illustrative tokens示例 Token

Room remaining剩余空间4,000

Toggle sample tools · fixed values, not a tokenizer勾选示例工具 · 固定数值,非实际分词计数

WHAT IS ON THIS RECEIPT?这张账单,记了什么?

Make the hidden
overhead visible.
让看不见的开销,
有一张清楚的账单。

Tool names look small in a settings panel. Their descriptions and parameter schemas can be much larger. ctxtax reads actual definitions and reports the cost at tool and server level.设置面板里的工具名称很短,背后的描述和参数结构却可能很长。ctxtax 读取实际定义,按工具和服务器列出开销。

  1. 01

    Inspect the definitions读取实际定义

    Connect to configured MCP servers and collect the tool schemas they expose.连接配置中的 MCP 服务器,获取它们公开的工具定义。

  2. 02

    Count with a baseline相对基准计算

    When configured, use the provider token-count endpoint to compare a request with and without a tool. Otherwise label the result as an estimate.配置计数服务后,比较包含与不包含工具的请求;使用估算方式时,明确标注为估算。

  3. 03

    Find the expensive details找到占用大的细节

    A sorted report and lint suggestions make long descriptions, large enums and verbose schemas easier to review.排序报告和 lint 建议帮助检查冗长描述、大型枚举与复杂参数结构。

A smaller budget
starts with a clear breakdown.
从一份明细开始,
理解你的上下文预算。

The tool includes per-tool reporting, schema linting and a model for deferred tool loading. The interactive budget on this page uses intentionally fixed example values.工具包含逐项报告、schema 检查与延迟加载的预算模型。本页交互使用固定示例数值,展示预算如何随所选工具变化。

KEEP ROOM TO THINK.留出思考的空间。

Know what fits.
Keep room to think.
算清占用,
留出思考的空间。

Next project下一个项目Looming