Skip to main content
Glama

run_estimate

Price a run (free, no side effects). Costs are in credits.

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": {
      "document_id": "<document_id>"
    },
    "name": "run_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
block_idsNo
document_idYes
template_idNo
workflow_idNo
updated_onlyNo
parallel_modeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose two important traits - the call is free and has no side effects - which is real behavioral value for a pricing endpoint, but it says nothing about permissions, what happens with invalid documents/templates, or what the estimate covers.

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?

Two short sentences with the key constraint front-loaded and zero padding. It is difficult to trim further, though the brevity itself is part of the under-specification problem.

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

Completeness2/5

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

For a six-parameter tool with no annotations, no output schema and no parameter documentation, this description is far too thin. An agent knows the call is safe and returns credits, but not what any parameter does or what a valid invocation looks like.

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

Parameters2/5

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

Six parameters with 0% schema description coverage, and the description explains none of them: document_id, block_ids, template_id, workflow_id, updated_only and parallel_mode are all left opaque. The single hint, "Costs are in credits", describes output units rather than input meaning, so it does not compensate for the coverage gap.

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?

"Price a run" names a specific verb (price) and resource (run), and combined with the credits note an agent can tell this computes a cost estimate rather than executing anything. It does not distinguish itself from the sibling group_run_estimate, so the differentiation is only partial.

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?

"free, no side effects" strongly implies this is the preview step before run_start, but the connection is never stated and no alternative or exclusion is named. An agent can infer when to use it, but must do the inference itself.

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