Skip to main content
Glama

Get an API request

get_api_request
Read-only

Use this when the user wants the details of one past call, such as how it ended or what it cost. Returns the request with its route, status, time, cost and units, the key that made it, the address it came from and, for a charged call, the balance after its charge. Request and response bodies are never kept, so it cannot show what a call sent or returned. Only requests of the last 30 days exist. Free.

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": {
      "requestId": "<requestId>"
    },
    "name": "get_api_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestIdYesThe request's id, as its X-Request-Id header and the requests list give it.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/non-destructive annotations it discloses genuinely useful limits: request and response bodies are never retained, only requests from the last 30 days exist, and the call is free. It also enumerates exactly which fields come back (route, status, time, cost, units, key, source address, post-charge balance), which prevents an agent from promising data the tool cannot return.

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?

Guidance is front-loaded in the first sentence, limitations follow, and every clause carries information. The middle sentence is a long enumerated field list, which is dense but justified; there is no filler.

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?

There is no output schema, and the description compensates by describing the returned record's fields, plus the two constraints (no bodies, 30-day window) an agent needs to answer correctly. Nothing material is missing for a single-parameter read tool.

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 requestId property already explains the id, its format, and that it comes from the X-Request-Id header or the requests list. The description adds nothing further about the parameter, so the schema carries that burden; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: retrieve the details of one past API request/call. The phrase 'one past call' implicitly contrasts with the sibling list_api_requests, letting an agent distinguish single-item lookup from listing without opening either schema.

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 opening 'Use this when the user wants the details of one past call, such as how it ended or what it cost' gives clear triggering context. It does not name an alternative or state when not to use it, so it stops short of full routing guidance.

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