Skip to main content
Glama

group_run_get

Poll a group run: rollup + per-language lanes.

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": {
      "group_run_id": "<group_run_id>"
    },
    "name": "group_run_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_run_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden and largely fails it. "Poll" weakly implies a read-only operation, but there is no statement about permissions, rate-limit behavior for polling, terminal versus in-progress states, or what happens when the run does not exist.

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?

A single compact phrase with no filler, and the core action is front-loaded. Its brevity is efficient rather than padded, though it borders on under-specification for a polling endpoint.

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?

With no annotations and no output schema, the description is the only source of behavioral context, yet it never explains what "rollup" and "per-language lanes" actually mean or how the agent should interpret an in-progress result. For a polling tool whose value depends on interpreting status over repeated calls, this is a notable gap.

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?

Schema description coverage is 0% for the single required parameter group_run_id, and the description never mentions it, its format, or where an agent obtains one (presumably from group_run_start or group_run_list). The description therefore adds no meaning beyond the bare schema type.

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?

"Poll a group run" gives a specific verb plus resource, and "rollup + per-language lanes" indicates what the response contains. It does not distinguish itself from the closely named sibling run_get, leaving the agent to infer that this operates on a group run rather than a single run.

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 word "Poll" implies repeated invocation to check progress, but there is no explicit when-to-use, no when-not, and no reference to alternatives such as group_run_list or run_get. An agent gets no guidance on when this tool is the right choice over the sibling retrieval tools.

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