Agent Action Gateway

Get order

get_order

Read-only

Retrieve a single WooCommerce order by numeric ID to view status, total, items, refunded amount, and customer first name; read-only.

Instructions

Look up one store order by its numeric ID. Returns status, total, items, refunded amount and the customer first name. Read-only.

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_id": "<order_id>"
    },
    "name": "get_order"
  }
}

Input Schema

Name	Required	Description	Default
`order_id`	Yes	The numeric WooCommerce order ID, e.g. 20

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

A3.5/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true, and the description's closing "Read-only" merely restates that, earning no credit. The valuable addition is the disclosure of what the response contains (status, total, items, refunded amount, customer first name), which compensates for the absent output schema. Nothing is said about not-found or invalid-ID behavior.

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 short sentences, front-loaded with the operation and followed by the return payload. The final "Read-only" clause is redundant against the readOnlyHint annotation, which is the only wasted wording.

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 lookup with no output schema, the description covers both what to supply and what comes back, which is the key gap it needs to fill. It is slightly incomplete on failure modes (invalid or nonexistent ID) and on any pagination or expansion options, but the core is covered.

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%, so the order_id parameter is fully documented in the schema, including its numeric type and example. The description adds only the word "numeric" and the notion of it being the store order ID, which is marginal beyond the schema. Baseline 3 applies when the schema carries the semantics.

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?

"Look up one store order by its numeric ID" gives a specific verb, resource and cardinality, which implicitly separates it from the sibling search_orders. It also enumerates the fields returned. It stops short of naming the sibling as the alternative, so it is clear but not fully differentiated in the definition itself.

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: the phrase "one store order by its numeric ID" signals that this is a single-record fetch rather than a search, but there is no explicit when-to-use statement, no exclusion, and no named alternative such as search_orders. An agent must infer the routing from the cardinality wording.

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

Deploy Server