tokencast

Overview Schema Source Related Servers Discussions Admin

estimate_cost

Estimate Anthropic API token costs for a development plan before execution, enabling cost-aware planning for LLM agent workflows.

Instructions

Estimate Anthropic API token costs for a development plan before execution

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "size": "<size>",
      "files": "<files>",
      "complexity": "<complexity>"
    },
    "name": "estimate_cost"
  }
}

Input Schema

Name	Required	Description	Default
`size`	Yes
`files`	Yes
`steps`	No
`language`	No
`complexity`	Yes
`file_paths`	No
`project_type`	No
`review_cycles`	No
`avg_file_lines`	No
`parallel_groups`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4Aug 2, 2026

TDQS

B3.2/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It states the tool estimates costs, implying a non-mutating calculation, but does not reveal whether it makes network calls, how the estimate is computed, what the return format is, or any side effects. For a tool with 10 parameters, this is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence of under 15 words. It contains no fluff and efficiently communicates the core purpose, achieving high clarity per word.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is complex (10 params, no output schema, no annotations), yet the description provides only a minimal one-sentence purpose. It gives no information about expected inputs, output structure, or behavioral nuances, making it wholly inadequate for an agent to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, and the tool description does not explain any of the 10 parameters. Required fields like size, files, and complexity are not mentioned, and even the enums (XS/S/M/L, low/medium/high) are left undocumented. The description fails to compensate for the schema's lack of semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Estimate') and identifies the resource ('Anthropic API token costs') and context ('for a development plan before execution'). This clearly distinguishes it from sibling tools that report or record costs, making its purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'before execution' provides clear contextual guidance for when to use this tool, implying it is for planning rather than after-the-fact reporting. However, it does not explicitly name alternative tools or state when not to use it, so it falls short of the highest bar.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server