Skip to main content
Glama
Sign In
wp-ssh-mcp

wp-ssh-mcp

by MSSOFTPC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

order_get

order_get
Read-onlyIdempotent

Retrieves complete WooCommerce order details, including line items and shipping and billing addresses, by order ID.

Instructions

Full order detail including line items and addresses.

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": "order_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesOrder ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/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, so the safety profile is covered. The description earns credit for disclosing that the payload includes line items and addresses (useful for deciding whether a follow-up call is needed), but says nothing about missing-ID behavior, errors, or payload size.

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?

One short sentence with zero filler, front-loaded on the most decision-relevant fact (that full detail comes back). It is slightly telegraphic as a sentence fragment, but no sentence wastes space.

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 simple read-only getter with one required param and no output schema, the description adequately signals the return contents. However, it leaves open the list-vs-get routing question and any failure/empty-result behavior, which the agent would need given there is no output schema.

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?

Single parameter with 100% schema description coverage ("Order ID"), so the schema carries the meaning. The description adds nothing about the id beyond what the schema already states; 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?

"Full order detail including line items and addresses" names the resource (order) and the depth of detail returned, which implicitly separates it from the sibling order_list. It is a noun phrase rather than a verb+resource statement, so the action (retrieve one order by ID) is only inferable.

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?

No when-to-use guidance and no alternative named; the agent must infer from the name/description alone that this is the single-order lookup versus order_list. No preconditions or fallback behavior are stated.

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

Deploy Server

Other Tools