Skip to main content
Glama

Read an order request

get_order_request
Read-onlyIdempotent

Read one order request: the products and quantities, the visitor's name, phone, email, delivery address and note, the internal note and the chat it came from. Needs the Standard plan or higher.

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_number": "<request_number>"
    },
    "name": "get_order_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_numberYesThe number, for example ORD-37779, from list_order_requests.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds value beyond that by disclosing the plan/tier requirement and by listing what fields come back, which matters since there is no output schema.

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?

Two tight sentences with the core action front-loaded; the field enumeration, while list-like, is doing real work as return-value disclosure. No filler or repetition of the title.

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?

For a single-parameter read tool with full schema coverage, the definition covers what it returns, what is required to call it, and where the identifier comes from. It does not mention failure behavior (unknown request number, plan too low producing an error), which is the only notable gap.

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 schema itself gives the format example ORD-37779 and the provenance ('from list_order_requests'). The description adds nothing further about the parameter, so the 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?

The description gives a specific verb and resource ('Read one order request') and immediately enumerates the contents returned (products, quantities, visitor contact details, addresses, notes, source chat). The word 'one' plus the request_number parameter clearly separates it from list_order_requests and update_order_request, so an agent can pick it without opening a sibling schema.

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?

It states a real prerequisite ('Needs the Standard plan or higher'), which is useful selection context, and the schema note says the number comes from list_order_requests. However, it never explicitly says when to use this versus list_order_requests or update_order_request, so the retrieval-vs-list distinction is only implied.

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