Skip to main content
Glama

cost_estimate

Read-onlyIdempotent

Monthly cost of a workload on every paid model at list prices, cheapest first. Excludes caching and volume discounts.

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": {
      "input_millions": "<input_millions>",
      "output_millions": "<output_millions>"
    },
    "name": "cost_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
labNoOptional lab or model words to filter
limitNoMax results, default 10, max 50
input_millionsYesInput tokens per month, in millions
output_millionsYesOutput tokens per month, in millions

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the description adds context rather than carrying the safety burden. It does add genuinely useful behavioral caveats that annotations cannot convey: pricing is at list rates, and caching and volume discounts are excluded, which directly affects how an agent should interpret results. It does not state whether unknown or filtered-out models are omitted silently.

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 tight sentences with no filler. The primary purpose is front-loaded, and the second sentence carries a distinct and necessary caveat rather than restating the first.

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?

For a read-only cost calculator with a fully described four-parameter schema, the definition covers purpose, pricing basis, output ordering and exclusions. With no output schema, a brief note on what each result row contains (model identity plus monthly cost) would close the remaining gap, but nothing essential is missing.

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 every parameter (lab, limit, input_millions, output_millions) is already documented in the schema with units and defaults. The description adds only the phrase 'every paid model', which conveys scope (paid models only) but no per-parameter meaning 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 states a specific computation and scope: monthly cost of a workload across every paid model at list prices, ordered cheapest first. That is far more informative than the bare name 'cost_estimate'. It does not explicitly contrast itself with the list_models sibling, though the verb+resource difference (costing a workload vs. listing models) is self-evident.

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 the tool to reach for when comparing monthly spend across models. There is no explicit when-to-use statement, no noted alternatives (e.g. list_models for catalog browsing), and no stated prerequisites or exclusions.

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