Read the payment and delivery status of an order using its private token or an authorized connection. A paid order is not necessarily delivered.
| Name | Required | Description | Default |
|---|---|---|---|
| orderId | Yes | ||
| orderToken | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / additionalPropertiesRemoved value: -falseDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare read-only, idempotent, and non-destructive behavior. The description goes beyond them by explaining the required access mechanism (private token or authorized connection) and adding the important domain caveat that payment status does not guarantee delivery. No contradiction with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tightly written sentences with no filler. The core purpose is front-loaded, and the second sentence earns its place by adding a non-obvious interpretation rule.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only getter, the description covers purpose, access, and a domain nuance. However, it omits how orderId and orderToken interact and does not explain what happens when the order is not found or the connection is unauthorized. These gaps matter because no output schema exists to fill them.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has no property descriptions and 0% coverage, so the description must compensate. It partially explains orderToken as the 'private token', but it never explains the role of the required orderId, the relationship between orderId and orderToken, or when each auth path applies. This is a meaningful gap for a tool with one required parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a specific action, 'Read', names the resource as 'the payment and delivery status of an order', and clarifies the auth path. This distinguishes it from mutating siblings such as create_order and pay_order, and the added statement 'A paid order is not necessarily delivered' sharpens its semantic scope.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It clearly indicates when to use the tool: when you need to inspect an order's payment and delivery state without modifying it. It does not explicitly name alternatives or exclusions, but the read-only framing and sibling names make the intended use obvious enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool maps to a distinct resource or action: profile lookup, post listing, service listing, quoting, order creation, payment, order status, and wallet balance. The only adjacent pair is list_services/get_quote, but their descriptions explicitly separate catalog pricing from exact quote calculation.
All tool names follow a consistent lowercase snake_case verb_noun pattern: get_* for single resources, list_* for collections, and create_order/pay_order for lifecycle actions. No mixed naming conventions or vague verbs appear.
Eight tools is well-scoped for a social media engagement purchasing server. Each tool covers a necessary step in the quote-to-delivery workflow without redundancy or unnecessary surface area.
The tool set covers the full lifecycle: discover services, inspect profiles/posts, get a verified quote, create an unpaid order, check wallet balance, pay, and track order status. No critical gap prevents an agent from completing the intended purchase flow.