Skip to main content
Glama

request_status

Read-onlyIdempotent

Check the status of a pending ask() job.

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": "request_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesJob id returned by a prior ask() call that went async.
publisher_idNoPublisher the research is bound to. Only the dedicated research credential may send it; other callers are refused.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / publisher_id
      Added value: +{
      +  "description": "Publisher the research is bound to. Only the dedicated research credential may send it; other callers are refused.",
      +  "type": "number"
      +}
  2. First observed

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds almost nothing beyond that: no polling cadence, no terminal-state behavior, and no indication of how long results remain retrievable. 'Pending' is the only behavioral nuance contributed.

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 front-loaded sentence with the verb first and zero filler. It is efficient, though its brevity is close to under-specification rather than disciplined conciseness.

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?

No output schema exists, so the description is the only place an agent could learn what 'status' actually returns (e.g. pending/complete/failed) and whether to retry, yet it says nothing about return values. For a simple two-parameter read tool this is a modest but real gap, especially with a sibling like read_response that presumably supplies results.

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 coverage is 100%, and the schema descriptions already explain that job_id comes from a prior async ask() call and that publisher_id is restricted to the dedicated research credential. The description duplicates none of this and adds no extra meaning, so the baseline of 3 applies.

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?

States a specific verb and resource: 'Check the status of a pending ask() job.' The reference to ask() scopes it to async jobs spawned by a named sibling, so an agent can broadly tell it apart from read_response. It stops short of explicitly contrasting the two, so it lands at 4 rather than 5.

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?

The word 'pending' implies this is the polling tool for jobs that haven't finished, which is usable context. There is no explicit statement of when to call it versus read_response, how often to poll, or what to do once the job is no longer pending.

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