Estimate Request Cost
estimate_request_costRates a planned request's likely token cost as LOW, MEDIUM or HIGH, with reasons and cheaper alternatives. Use before documentation-heavy or project-wide work to narrow scope.
Instructions
Rates a planned request's likely token cost as LOW, MEDIUM or HIGH, with the reasons and cheaper ways to do it. It is a keyword heuristic over the request text and the planned tool names, with no project or IDE access and no real token count, so treat it as a prompt to narrow scope rather than a measurement. Most useful before documentation-heavy or project-wide work.
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": {
"request": "<request>"
},
"name": "estimate_request_cost"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| request | Yes | The task in plain words, e.g. 'Add a ListBox to Window1'. Longer text and words such as 'entire', 'refactor' or 'docs' raise the rating. | |
| planned_tools | No | Comma-separated tool names you expect to call, e.g. 'search_docs, get_code'. Only list_doc_topics, lookup_class, search_docs, get_code and set_code affect the rating. |