Skip to main content
Glama

getOrderById

Read-onlyIdempotent

Fetch a purchase order by its ID to retrieve order details for a specific order.

Instructions

Find purchase order by ID.

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": {
      "orderId": "<orderId>"
    },
    "name": "getOrderById"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderIdYesID of order that needs to be fetched

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully carried by structured data. The description adds no behavior beyond that - it does not say what happens when no order matches the ID or what the response contains. With annotations carrying the load, a minimal description is acceptable but contributes little.

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 four-word sentence with zero waste, and the resource and lookup key are front-loaded. It is efficient but borders on terse given there is essentially one clause of content.

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?

For a one-parameter read-only lookup with no output schema and full annotation coverage, the definition is largely sufficient. Missing are not-found/error behavior and any hint about the returned order shape, which the absent output schema leaves undocumented.

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?

There is a single required parameter with 100% schema description coverage ("ID of order that needs to be fetched"), so the schema fully documents it. The description adds no format, range, or example detail beyond the schema, so the baseline 3 applies.

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?

The description gives a specific verb and resource ("Find purchase order") and scopes it to lookup by ID. What it lacks is any differentiation from the near-identical sibling lookups such as getPetById and getUserByName, so the agent knows the resource but not why one beats another.

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 explicit when-to-use or when-not-to-use guidance and no named alternative. The only signal is the implicit "by ID" framing, which a caller must infer selects this tool over the list-style siblings like findPetsByStatus.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.