Skip to main content
Glama

group_run_estimate

Price a multi-language fan-out (free).

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>",
      "target_languages": "<target_languages>"
    },
    "name": "group_run_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
block_idsNo
document_idYes
template_idNo
workflow_idNo
updated_onlyNo
parallel_modeNo
target_languagesYes
include_untranslatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It adds one useful fact (the call is free, i.e. incurs no billing), but omits whether it is read-only/non-executing, what it returns, and how the eight scope parameters (block_ids, template_id, workflow_id, parallel_mode) change the priced unit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded fragment with no wasted words, but the terseness crosses into under-specification rather than efficiency. A few more words naming the return value and the sibling would cost little and add much.

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 an eight-parameter tool with no annotations, no output schema, and no parameter documentation, this description is far too thin. An agent cannot determine what the returned price covers or how target_languages="all" versus a list affects the result.

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

Parameters1/5

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

Schema description coverage is 0% across eight parameters, including the two required ones (document_id, target_languages) and the complex block_ids union of array-or-object. The description explains none of them, so an agent gets zero semantic guidance on how to scope the estimate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Price a multi-language fan-out" supplies a verb (price) and a resource (multi-language fan-out), so the agent can infer a cost-estimate operation for a group run. However, "fan-out" is internal jargon and the description never says it estimates a group run without executing it, nor does it distinguish this from the sibling run_estimate for single runs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage signal is the parenthetical "(free)", which implies this is a safe pre-flight check before group_run_start, but that is inference. There is no explicit when-to-use, no mention of run_estimate as the single-run alternative, and no stated prerequisites such as needing an existing document or template.

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