Skip to main content
Glama

kiri_estimate

Use this for any question about what a Kiri request might cost before you spend. It returns a cost range and the maximum hold, and it does not run Kiri. Grades and PSA lookups on a live request are charged at their listed prices. Free, limited to 30 per minute and 300 per key per UTC day.

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": {
      "message": "<message>"
    },
    "name": "kiri_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesThe request you might send to kiri_chat
max_cost_usdNoOptional cap in dollars. The range shows whether a live request would fit.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses that the tool does not run Kiri, returns a cost range and maximum hold, notes live-request billing for grades and PSA lookups, and specifies free usage plus rate limits of 30 per minute and 300 per key per UTC day.

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 front-loaded with the core purpose and then adds only relevant behavioral details: return values, non-execution, billing context, and rate limits. There is no redundant or wasted wording.

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

Completeness5/5

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

Given that an output schema exists and schema coverage is complete, the description provides the remaining behavioral context an agent needs: it does not execute requests, what it returns, pricing caveats, and rate limits. Nothing material appears missing for correct invocation.

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 both message and max_cost_usd. The description adds high-level context about cost range and maximum hold but does not add parameter-specific meaning beyond what the schema provides.

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 states a specific purpose: estimating what a Kiri request might cost before spending, returning a cost range and maximum hold. It explicitly clarifies that it does not run Kiri, which distinguishes it from execution-oriented siblings such as kiri_chat.

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?

It clearly says to use this for cost questions before spending, and the non-execution behavior implies when not to use it. However, it does not explicitly name alternative pricing tools or exclusion cases, so it falls short of fully explicit when/when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources