Kingy AI Facts

Estimate a monthly API bill

estimate_monthly_bill

Read-onlyIdempotent

Turn a daily usage pattern (requests per day, tokens per request) into a cost per day and per period for up to six models, using Kingy's currently verified rates. Models without a current price are listed as unavailable with the reason.

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": {
      "models": "<models>",
      "requests_per_day": "<requests_per_day>",
      "input_tokens": "<input_tokens>",
      "output_tokens": "<output_tokens>"
    },
    "name": "estimate_monthly_bill"
  }
}

Input Schema

Name	Required	Description
`days`	No	Days in the period. Default 30.
`models`	Yes	Models to compare.
`input_tokens`	Yes	Input tokens per request, including any cached input.
`output_tokens`	Yes	Output tokens per request, including reasoning tokens.
`requests_per_day`	Yes	Requests per day.
`cached_input_tokens`	No	Portion of input_tokens served from the prompt cache. Default 0.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A3.5/5.0

Behavior3/5

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

The annotations already declare a read-only, idempotent, non-destructive, closed-world operation, so safety is covered. The description usefully adds that rates are 'currently verified' and that unpriced models come back as unavailable with a reason, which tells the agent to expect partial results. Beyond that it says nothing about rounding, currency, or how stale rates are handled.

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

Conciseness4/5

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

A single front-loaded sentence that leads with the input pattern and follows with the outputs and the failure mode for unpriced models. Every clause carries information; it is dense but not padded.

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

Completeness4/5

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

With no output schema, the description carries the burden of describing returns, and it does indicate both a per-day and per-period cost plus an unavailable-models-with-reason shape. What is missing is orientation relative to estimate_api_cost, the closest sibling, which matters for a six-parameter tool in a crowded cost-estimation family.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents every parameter including the default of 30 days and cached-input handling. The description only restates 'requests per day, tokens per request' and the six-model cap, adding no syntax or interpretation guidance beyond the schema. Baseline 3 applies.

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

Purpose4/5

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

The description names a concrete verb and resource: turning a daily usage pattern (requests per day, tokens per request) into a cost per day and per period for up to six models. That is specific enough for an agent to know what the tool produces. It does not, however, distinguish itself from the sibling estimate_api_cost, which sounds like a near-duplicate.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is for projecting spend from usage assumptions, but the description never states when to pick it over estimate_api_cost or compare_subscription_plans. There are no exclusions, prerequisites, or alternative routing.

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

All Kingy AI Facts tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?