Skip to main content
Glama

List Requests

list_requests
Read-onlyIdempotent

List the person’s Requests and what needs attention on each: a new Offer, a question, missing details or a check that they still want it.

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_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNonext_cursor from the previous page.
statusNoopen (the default), closed or all.open

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / result / properties / can
      Added value: +{
      +  "type": "array"
      +}
    • changedOutput schema / properties / result / required
      Previous value: -[
      -  "requests",
      -  "next_cursor"
      -]New value: +[
      +  "requests",
      +  "next_cursor",
      +  "can"
      +]
  2. Added

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 scope, so safety is covered. The description adds useful context about what each row signals (a new Offer, an unanswered question, missing details, a re-confirmation), but says nothing about ordering, page size, or what the cursor yields.

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 front-loaded sentence that names the resource first and then enumerates the attention signals. No redundant or filler wording.

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?

An output schema exists, so return values need not be spelled out, and annotations carry the safety profile. For a two-parameter, zero-required list tool the description supplies exactly what an agent needs to choose and call it.

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% and both parameters (cursor, status with enum open/closed/all) are fully documented in the schema, so baseline 3 applies. The description adds no extra meaning about default scoping beyond the schema's stated default of open.

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 ("List the person's Requests") plus the per-item payload of attention states (new Offer, question, missing details, confirmation check). This distinguishes it from write siblings like close_request or update_request, though it never contrasts with the singular get_request.

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?

Usage is implied rather than stated: an agent can infer this is the triage/overview call and that per-item detail lives elsewhere, but there is no explicit when-to-use or when-not-to-use instruction and no named alternative for drilling into a single request.

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