Skip to main content
Glama

Get a group-maker result

get_group_result
Read-only

Fetch the result of a make_groups job that returned status 'running'. Waits up to wait_seconds; call again while status is 'running'. Jobs expire 15 minutes after they finish.

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": {
      "job_id": "<job_id>"
    },
    "name": "get_group_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
wait_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior the annotations cannot convey – the blocking wait and the 15-minute post-completion expiry for jobs – but says nothing about what an expired or failed job returns or how errors surface.

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?

Three short sentences, each carrying a distinct fact – what it fetches, how long it blocks, how to poll, when data disappears – with the most decision-relevant detail first. No filler or restatement of the title.

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?

Covers the call pattern, timing behavior and expiry for a two-parameter polling tool with no output schema. The main remaining hole is the shape of the 'result' payload, which an agent must discover after the fact, but nothing prevents correct invocation.

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 0%, so the description has to carry both parameters. It does explain wait_seconds semantics ('Waits up to wait_seconds') but omits the 45-second cap's implication and any default, and never characterizes job_id beyond context. Partial compensation for a documented-schema gap.

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

Purpose5/5

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

Names a specific verb ('Fetch') and resource ('the result of a make_groups job'), and pins the tool to jobs in the 'running' state, which clearly separates it from the sibling make_groups that starts a job. An agent can distinguish it from the other siblings without opening any schema.

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?

Gives an explicit polling instruction: 'call again while status is running', and frames wait_seconds as bounding the wait. It stops short of naming alternatives such as check_request when the job state is unknown, so the guidance is clear but not exhaustive.

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