Skip to main content
Glama

Get a Request

get_request
Read-onlyIdempotent

Read one Request: what the person asked for, its items and options, open questions, notification settings and a summary of any Offers.

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": {
      "request_id": "<request_id>"
    },
    "name": "get_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNosummary (the default) or full, the whole Request with its history.summary
request_idYesThe Request’s id from list_requests.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds scope detail by saying Offers appear only as a "summary," hinting that full offer data lives elsewhere, but it says nothing about mutation risk, permissions, or failure modes that the annotations do not already cover.

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 leads with the verb and resource, then enumerates returned content with no filler. The list runs slightly long compared to what the output schema already conveys, but nothing is wasted.

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 a rich annotation set, a full output schema, and 100% parameter coverage, the description only needs to establish scope and purpose, which it does. The remaining gap is routing guidance against the many sibling tools, which would be nice but is partially mitigated by the request_id pointer to list_requests.

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 request_id (UUID from list_requests) and the summary/full enum are fully documented in the schema itself. The description adds no meaning beyond that, so the baseline of 3 applies – it neither compensates for nor undermines the schema.

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 ("Read one Request") and enumerates the substance returned: items, options, open questions, notification settings, and an Offers summary. That is far more useful than a tautology, though it never names a sibling such as list_requests or get_offers to sharpen the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance. It never explains when an agent should pick this single-request read instead of list_requests or get_offers, nor when the detail=full mode is warranted, leaving usage entirely implicit in the schema.

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