Skip to main content
Glama

ADS Beast

get_job_result

Read-only

Result of a call that answered status running with a job_id: running (poll in 15 s), done with the result, failed with why, or expired (24 h). Same key only; not metered.

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_job_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesThe job_id from a tool answer with status 'running'.

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 declare readOnlyHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuinely new operational context the annotations cannot express: the four terminal states (running, done, failed, expired), the 24-hour expiry, the requirement to use the same key, and that the call is not metered. It does not describe the shape of the returned result on 'done', which is the main remaining gap.

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 dense sentence that front-loads the outcome states and includes interval, expiry and cost notes with no filler. The clipped style ('Same key only; not metered') is efficient but slightly cryptic for a first-time reader.

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 single-parameter polling tool with no output schema, the definition covers the state machine, poll cadence, expiry, key scoping and metering — enough to call it correctly. The only omission is any indication of what the payload looks like on success or failure beyond 'the result' and 'why'.

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?

With one parameter at 100% schema coverage, the schema already explains job_id in full, so the baseline is 4. The description reinforces the provenance of the value (from a call that answered 'running') but adds no new format or constraint detail beyond the schema.

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?

The description names a specific resource (the result of an async call) and the precondition that produced it (a call answered with status 'running' and a job_id). It is not a tautology of the name, though the phrasing 'Result of a call that answered status running with a job_id' is telegraphic and requires a second read. No sibling is named, so no explicit differentiation is offered.

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?

It clearly implies the trigger condition: call this after a tool answered with status 'running' and returned a job_id. It also supplies concrete operational guidance ('poll in 15 s') and an expiry horizon (24 h), which tells the agent how long retries remain meaningful. It stops short of stating when not to use it or naming alternatives for retrieving data another way.

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.