Skip to main content
Glama

order_events

Read-onlyIdempotent

The order's history: revisions, checks, quotes and status changes.

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_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderYesOrder id (ord_…).

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo
summaryNo
warningsNo
next_actionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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=true, so the safety profile is fully covered. The description's only added behavioral value is naming the event categories returned; it says nothing about ordering, pagination, completeness, or authorization needs for a read on another party's order, which is where the real gap lies given openWorldHint.

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 twelve-word fragment with zero padding, front-loading the resource and then the contents. The only structural weakness is the missing verb, which trades a little clarity for compactness.

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?

An output schema exists, so return values need no explanation, and the annotations plus fully documented single parameter cover most of the structural burden. What remains unaddressed is whether the history is returned newest-first, whether it is truncated or paginated, and how it relates to the other order_* readers — details an agent would need to interpret the result.

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 ('Order id (ord_…)'), so the schema carries the full semantic burden and the baseline of 3 applies. The description adds no format or scope hints for the order argument beyond what the schema already states.

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 identifies the resource (an order's history) and enumerates the event kinds it covers (revisions, checks, quotes, status changes), which is more than a restatement of the name. However, it is a bare noun phrase with no verb, so an agent must infer that this is a read/retrieval operation, and nothing distinguishes it from order_show or order_quote beyond the word 'history'.

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 guidance at all: no mention of when to prefer this over order_show for current state, or over order_quote for quote details. Usage is only implied by the word 'history', leaving the agent to guess at alternatives.

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