Skip to main content
Glama

get_store_order

Read-onlyIdempotent

Read an order's line items, totals, tracking and refund status in the approved business.

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": {
      "id": "<id>"
    },
    "name": "get_store_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds the scoping constraint ("in the approved business") and the fact that tracking and refund status are included in the payload, but says nothing about what happens when the id is unknown or not in the approved business.

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

Conciseness5/5

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

A single front-loaded sentence with no filler; every clause (line items, totals, tracking, refund status, business scope) conveys distinct information. Nothing is repeated from the schema or annotations.

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 one param, no output schema and full annotation coverage, the description is largely sufficient and usefully previews the returned fields in place of an output schema. The only remaining gap is the meaning of the `id` argument and any failure behavior for missing or out-of-scope orders.

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 exactly one parameter, and the schema already fixes it as a UUID string with an explicit pattern, so its type needs no explanation. The description does not clarify that `id` is the order identifier (as opposed to an order number or line-item id), which is the one semantic detail it could have added.

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 names a specific verb ("Read") and resource ("an order") and enumerates the data returned: line items, totals, tracking and refund status. That is clear enough to distinguish a single-order fetch from list_store_orders or get_store_order_reconciliation, though it never names those siblings explicitly.

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 only implied: it reads one order, scoped to "the approved business." There is no explicit statement of when to prefer this over get_store_order_reconciliation, nor any prerequisite or exclusion, so the agent must infer the boundary from the verb alone.

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