Every request your agent makes carries every tool definition this server exposes — context your code, documents and conversation can't use, mostly for tools the agent never calls. You don't need them all in the window, and you don't have to pay for them.
QUICK ANSWER The Taskwarrior MCP server's 3 tool definitions consume 102 tokens — 0.1% of a 200k context window, and below the median MCP server (2,069 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.
Tool definitions are overhead: they occupy context on every request and compete with your code, documents and conversation history for the same window.
Corpus context: Taskwarrior ranks #3353 of 3,354 measured MCP servers by definition cost. The median is 2,069 tokens, p90 is 11,359, and the heaviest (SmartBear MCP) is 137,725 — 69% of a 200k window on its own. New to this? See MCP token cost and context window in the glossary.
Token cost is one axis. See the risk picture across your whole stack →
Each row is one tool definition as a tools/list entry — name, description and
input schema — counted with o200k_base. Average: 34 tokens per tool.
| Tool | Category | Tokens | % of server |
|---|---|---|---|
| mark_task_done | Write | 36 | 35.3% |
| get_next_tasks | Read | 35 | 34.3% |
| add_task | Write | 31 | 30.4% |
You don't need all 3 of those definitions in the window. PolicyLayer is an MCP gateway that sits in front of Taskwarrior: only the tools you grant are exposed to the agent, the rest never load. A smaller window means a sharper agent — less noise when it picks a tool — and every request costs less:
At 3 tools, Taskwarrior is already a small surface — the win here is policy control and audit rather than token savings.
Instant setup, no code required.
Model your own stack in the token-cost calculator, or see the Taskwarrior policy for what a sensible grant looks like.
Its 3 tool definitions total 102 tokens — 0.1% of a 200k context window — measured with tiktoken o200k_base over the serialised tools/list payload. Exact counts vary slightly by client and model.
MCP clients load every connected server's tool definitions — name, description, and input schema — into the model's context so it knows what it can call. That payload is charged against your context window on every request, whether or not a tool is used.
Expose fewer tools. A PolicyLayer grant scopes Taskwarrior to only the tools you allow — ungranted definitions are filtered out of the tool list, so they never enter the context window.
Partially, in some clients. Claude Code defers MCP tool schemas behind a tool-search step by default, and VS Code has experimental grouping — but you still pay tokens per search and reload, and Cursor, Windsurf and Gemini CLI load definitions upfront. Reducing the exposed tool set cuts the cost in every client.
Each tool is serialised as a tools/list entry — name, description, input schema — from the schemas in the PolicyLayer scan database. Clients differ slightly in framing, so treat counts as close estimates.
tiktoken o200k_base (GPT-4o/o-series). Anthropic's current tokeniser isn't published, so Claude's exact counts will differ; for English text and JSON schemas the totals are close enough to treat these as estimates.
Some clients now defer schema loading (Claude Code's tool search; VS Code experimental grouping). You still pay per search and reload — and Cursor, Windsurf and Gemini CLI load everything upfront.
Computed 06-07-2026 from the PolicyLayer scan database over all 3 catalogued Taskwarrior tools. Counts refresh with every site build.
A PolicyLayer grant scopes Taskwarrior to the tools you actually allow. Ungranted definitions never load, and every call that does run is checked against policy first.
Instant setup, no code required.
43,000+ MCP servers and 220,000+ tools scanned and risk-classified.