Skip to main content
Glama

order_show

Read-onlyIdempotent

An order's status, spec, file check, address and quotes.

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": {
      "order": "<order>"
    },
    "name": "order_show"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderYesOrder id (ord_…).
includeNoExtra detail, e.g. issues.

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo
summaryNo
warningsNo
next_actionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

The annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the bar is lower. The description adds that the response includes status, spec, file check, address, and quotes, but it does not explain what 'file check' means, how missing orders are handled, or any rate-limit or permission context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence with no wasted words, but it is a fragment rather than a structured clarification. Its brevity contributes to ambiguity around the tool's action and scope rather than crispness.

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

Completeness3/5

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

The tool is a simple read operation with an output schema and rich annotations, so extensive behavioral detail is not required. Still, the description does not state the tool's action clearly or explain when to choose it over order_list, leaving a noticeable gap for selection among many order-related siblings.

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 schema already documents the 'order' and 'include' parameters. The description does not add meaning beyond what the schema provides for those parameters, making the baseline score of 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun phrase listing an order's status, spec, file check, address, and quotes, which implies a single-order detail view. However, it lacks a clear verb such as 'Retrieve' or 'Show' and does not explicitly distinguish this tool from order_list or order_events.

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 guidance on when to use this tool versus siblings like order_list or order_events, and no exclusions or prerequisites are stated. The description only hints that it retrieves order details, leaving the agent to infer the appropriate use case.

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