Skip to main content
Glama

List requests

listRequests
Read-only

Find requests you already created, newest first.

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": "listRequests"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo
limitNo
cursorNo
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds one useful behavioral fact not in annotations — results are returned newest first — but says nothing about pagination behavior despite a cursor parameter and a default/maximum limit.

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 short sentence with the key scoping fact front-loaded and no filler. It is efficient, though at this length it leaves no room to address the parameters — a terseness cost rather than a verbosity problem.

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

Completeness2/5

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

For a four-parameter list tool with two enums, a cursor, and no output schema, the description omits filtering dimensions, pagination mechanics, and default result counts. An agent can guess it is a listing call but cannot infer how to page or filter correctly.

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% across four parameters, so the description carries the full burden and does not compensate: mode, status (both enums), limit, and cursor are never mentioned. The only semantic hint is the implicit creator scope in 'you already created.'

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?

Names a specific verb+resource ('Find requests') and adds scope ('you already created') plus ordering ('newest first'), which distinguishes it from createRequest/updateRequest/closeRequest. It doesn't explicitly contrast with getStatus, but the listing nature is unmistakable.

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?

'Find requests you already created' implies when to reach for it (retrieving your own submissions) but gives no explicit when-not, no mention of the sibling tools it replaces (e.g., use getStatus for a single request), and no prerequisite context. Usage is inferable but not stated.

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