plan_mcp_token_budget
Plan and attribute MCP token spend across agents, servers and workflows — something the protocol provides no native support for. Outputs per-dimension cost split and a quota plan.
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": {
"workloads": "<workloads>"
},
"name": "plan_mcp_token_budget"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| workloads | Yes | JSON array of {name, callsPerDay, inputTokensPerCall, outputTokensPerCall, owner?}. Accepts a JSON array, or a JSON string containing one. | |
| monthlyBudget | No | Optional monthly budget cap in USD for over/under comparison | |
| inputPricePerMillion | No | Input price per 1M tokens in USD (default 3) | |
| outputPricePerMillion | No | Output price per 1M tokens in USD (default 15) |