Skip to main content
Glama

octadezx_verify_order

Read-onlyIdempotent

Verifies live order fulfillment status, line items, and totals before refunds or WISMO replies, helping prevent incorrect promises or cited amounts.

Instructions

Look up authoritative live order fulfillment status, line items, and verified totals in your connected OctaDezx storefront integration (Shopify or WooCommerce). Use before promising refunds, answering WISMO questions, or citing order amounts. Requires OCTADEZX_API_KEY; returns a structured 'requires_api_key' error payload if unconfigured.

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": {
      "orderId": "<orderId>"
    },
    "name": "octadezx_verify_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderIdYesStorefront order ID (for example, 'OD-1042' or '#1042') or verified customer phone number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.2.1
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / orderId / description
      Previous value: -"The order ID or customer phone number"New value: +"Storefront order ID (for example, 'OD-1042' or '#1042') or verified customer phone number."
    • addedInput schema / properties / orderId / minLength
      Added value: +1
  2. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior: an OCTADEZX_API_KEY requirement and a predictable 'requires_api_key' error payload when unconfigured, which tells the agent how failure will look. It does not mention rate limits or result-size limits, keeping it just below the top score.

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?

Three sentences, front-loaded with what the tool returns, then when to use it, then the auth/failure caveat. Every sentence carries distinct information and nothing is repeated from the title or schema.

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 no output schema, the description correctly compensates by enumerating the returned fields (status, line items, verified totals). Combined with the auth note and usage triggers, an agent has what it needs to call this correctly; only edge cases such as multiple matches for a phone-number lookup are unaddressed.

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 description coverage is 100%, and the schema already documents the single orderId field with concrete examples ('OD-1042', '#1042') plus the phone-number alternative. The description adds no additional meaning about that parameter, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb-plus-resource statement: it looks up 'authoritative live order fulfillment status, line items, and verified totals' from a connected Shopify/WooCommerce storefront. It also names the data source and its trust level ('authoritative live'), so an agent can immediately tell this apart from reply-safety, scheduling, or conversation-listing siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete when-to-use triggers: before promising refunds, before answering WISMO questions, and before citing order amounts. It stops short of stating when not to call it or naming an alternative tool for adjacent tasks, so it is clear context without explicit exclusions.

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