Skip to main content
Glama

AgentSupply

Check request status

get_request_status
Read-only

Check the status of a previously submitted request and read our reply (quote, result or decline).

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": {
      "request_id": "<request_id>",
      "status_token": "<status_token>"
    },
    "name": "get_request_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYes
status_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the reply is one of three outcome types, which is genuinely useful beyond the annotations. It does not disclose whether the status_token acts as a credential, whether results expire, or whether status changes over time.

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?

A single sentence that front-loads the action and the value returned, with no filler. Nothing could be cut without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With readOnly annotations and no output schema, the description partially covers the reply shape (quote/result/decline), which is the main thing an agent needs. The unexplained status_token and the absence of polling or expiry guidance leave meaningful gaps for a two-required-parameter lookup tool.

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%, so both parameters depend on the description. 'previously submitted request' loosely implies what request_id refers to, but status_token is never explained at all — a significant omission for what is likely a secret access credential.

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 gives a specific verb ('Check') and resource ('status of a previously submitted request'), and it names the kinds of reply the caller can expect (quote, result, decline). It is clearly distinguishable from submit_request, but it does not explicitly name or contrast any sibling tool.

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?

'previously submitted request' implies the tool applies only after a submission, which is useful implied usage guidance. There is no explicit statement of preconditions, polling advice, or what to do when no request exists yet.

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