Skip to main content
Glama

Inspect an original Ubi request

request_status
Read-onlyIdempotent

Recover a request's status using its original idempotency key. Rechecks caller scope and object access. Unknown outcomes may include committed changes; request_not_found does not authorize a duplicate.

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": {
      "idempotency_key": "<idempotency_key>"
    },
    "name": "request_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idempotency_keyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is contextual, and the description clears it: it discloses that caller scope and object access are re-checked at call time, and that 'unknown' outcomes can still have committed changes upstream, which is the non-obvious fact an agent needs before re-issuing anything. It also defines the meaning of the request_not_found result. No claim conflicts with the readOnlyHint.

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?

Three short sentences, verb-first, with the precondition ahead of the caveats; nothing is redundant. The telegraphic phrasing ('request_not_found does not authorize a duplicate') is dense but readable.

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

Completeness5/5

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

For a one-parameter lookup with an output schema and full annotation coverage, the description supplies exactly the missing piece: retry/duplicate semantics around an indeterminate status. Return values can be inferred from the output schema, so no gap remains that would cause a wrong call.

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?

Schema description coverage is 0% for the single parameter, so the description must compensate, and it does: 'original' idempotency key tells the agent not to synthesize a fresh key, which is the most likely misuse. It still says nothing about key format, length, or scope of uniqueness.

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 ('Recover a request's status') and the keying mechanism ('using its original idempotency key'), which is enough to distinguish it from the get_*/list_* siblings. It stops short of naming which tool to use instead when no idempotency key exists, so it is clear but not fully differentiated.

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 the precondition (you must hold the original idempotency key) and gives concrete guidance for the ambiguous case: an unknown outcome may hide committed changes, and a not-found result does not license a retry. That is real when-to-use/when-not-to-retry guidance, though no alternative tool is named for the no-key case.

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