Skip to main content
Glama

List API requests

list_api_requests
Read-only

Use this when the user wants to review or debug recent calls: every request of the last 30 days, newest first, with its status, time and cost. Filter by status class, route or time, or find one request by its id. A connection without full access sees only its own requests. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_api_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoA request id, matched exactly.
toNoOnly requests made before this time, in ISO 8601.
fromNoOnly requests made at or after this time, in ISO 8601.
cursorNoThe `nextCursor` of the page before.
apiKeyIdNoOnly this key's requests. A key without full access reads only its own.
endpointNoOnly requests to this route, as the requests name it.
pageSizeNoRequests per page.
statusClassNoOnly requests answered with a status in this class.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: a fixed 30-day retention window, newest-first ordering, the returned fields (status, time, cost), permission-based visibility ('a connection without full access sees only its own requests') and that the call is free. Pagination behavior beyond the cursor field is not described.

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?

The use case is front-loaded in the first clause, followed by scope, filters, permissions and cost, with no redundant sentences. Even the terse 'Free.' fragment carries information an agent would otherwise have to guess.

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?

With eight optional parameters, no output schema and annotations covering safety, the description does enough: it explains what comes back, in what order, over what window, and how permissions narrow results. Pagination mechanics and the relationship to get_api_request are the only notable omissions.

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 description coverage is 100%, so the baseline is 3. The description restates the filter surface (status class, route, time, id) and adds the ordering fact, but supplies no extra syntax or semantics for q, from/to, apiKeyId or cursor beyond what the schema already documents.

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 and resource plus scope details: every request of the last 30 days, newest first, with status, time and cost. It is clearly a listing tool, but it also claims it can 'find one request by its id', which overlaps the sibling get_api_request and blurs which tool to pick for a single lookup.

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?

'Use this when the user wants to review or debug recent calls' gives a concrete triggering context, and the 30-day window implies when-not-to-use for older data. It never names an alternative such as get_api_request for single-request retrieval, so routing between the two is left to inference.

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