Skip to main content
Glama

Estimate cost

estimate_cost
Read-only

Validate an input and quote the credits a generation would charge, without charging. The same validation generate runs.

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": {
      "model_id": "<model_id>",
      "input": "<input>"
    },
    "name": "estimate_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
model_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the description's added value is the two behavioral claims it makes: no credits are charged, and the validation run is identical to `generate`'s. That second point is genuinely useful because it tells the agent a successful estimate implies `generate` will accept the same input. It does not say how validation failures surface, which keeps it from a 5.

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?

Two short sentences, front-loaded with the core action and the no-charge guarantee, with zero redundant wording. Nothing could be removed without losing meaning.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and the read-only safety profile is covered by annotations. However, for a validation tool with a fully undocumented free-form `input` object, the description leaves the agent guessing what to pass beyond a pointer to `generate`'s validation.

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 0% and one parameter (`input`) is a free-form nested object with additionalProperties, so the schema itself explains very little. The description partially compensates by implying `input` has the same shape `generate` expects, but it says nothing about `model_id` or what fields `input` requires.

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?

States a specific verb pair and resource: validate input and quote credit cost for a generation, explicitly without charging. It also names the sibling it mirrors ("The same validation `generate` runs"), so an agent can distinguish it from `generate` without opening either schema.

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?

Usage is clearly implied: call this before `generate` to learn the credit price and confirm the input would pass validation, with the explicit note that nothing is charged. It lacks an explicit when-not clause (e.g., what to do if the estimate fails validation, or whether to skip it when cost is irrelevant), so it falls just short of a 5.

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