Skip to main content
Glama

Managed Nerds

estimate_status

Read-onlyIdempotent

Check an estimate you got earlier: still valid?, when it expires, whether a full quote was requested, revisions left. Send the token from its status_url.

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": {
      "token": "<token>"
    },
    "name": "estimate_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is added context. It delivers that by telling the agent exactly what is reported back — validity, expiry date, whether a full quote was requested, and remaining revisions — which is meaningful since there is no output schema. It does not mention whether the token can expire or what a lookup failure looks like.

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?

One tight sentence front-loads the action, then lists the four questions answered, then the token instruction last. The telegraphic question fragments ('still valid?, when it expires') are efficient rather than sloppy, though they read slightly clipped.

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 one-parameter read-only status lookup with no output schema and full annotation coverage, the description supplies both the input prerequisite (token from status_url) and the expected return fields. Nothing essential to invoking it correctly is missing; only edge behavior on expired or invalid tokens is unstated.

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

Parameters4/5

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

Schema coverage is 0% — the schema only declares an untyped string — so the description must carry the meaning, and it does by stating the token comes from the estimate's status_url. That single sentence is what saves the parameter from being an opaque blob. No format or length details, but the origin is the critical semantic.

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?

Specific verb ('check') plus specific resource ('an estimate you got earlier'), with the returned facts enumerated (validity, expiry, full-quote flag, remaining revisions). It implicitly distinguishes itself from creation-side siblings like preliminary_estimate by scoping to an estimate already issued, though it never names an alternative explicitly.

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?

The phrase 'an estimate you got earlier' plus 'Send the token from its status_url' gives a clear triggering condition and the prerequisite artifact needed. It stops short of saying when NOT to use it or which sibling to call instead (e.g. request_full_quote for a new quote), so it is context without 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