Skip to main content
Glama

Get a request's status

get_request_status
Read-onlyIdempotent

Get the status of a request made with request_resource: received, or resource available with its link.

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

Input Schema

NameRequiredDescriptionDefault
idYesRequest id returned by request_resource.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / id / description
      Added value: +"Request id returned by request_resource."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered. The description's only addition beyond that is the two possible status outcomes, which is useful but thin, and it says nothing about whether 'received' is terminal or whether repeated polling is expected.

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 sentence that front-loads the action and the originating tool. The outcome clause ('received, or resource available with its link') is grammatically loose but still earns its place by conveying the return states.

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 one-parameter read tool with no output schema, the description covers the action, the prerequisite tool, and the possible result shapes - enough to call it correctly. It lacks guidance on polling or terminal states, but the surface area of ambiguity is small.

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?

One parameter at 100% schema coverage, whose schema already documents that it is the id returned by request_resource. The description restates that provenance but adds no format or validation detail beyond the schema, 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?

A specific verb+resource ('Get the status of a request') tied explicitly to the tool that produces the id ('made with request_resource'). It also names the two possible outcomes ('received' vs 'resource available with its link'), which lets an agent distinguish it from request_resource. Slightly awkward phrasing of the outcome list keeps it from a 5.

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?

The description establishes context clearly: call this when you hold a request id issued by request_resource. It does not state exclusions, polling cadence, or how long to wait before calling, so it stops short of a 5.

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.