Skip to main content
Glama

WeBuyClubz — AI Golf Caddy, Club Catalog & Trade-In Engine

check_order_status

Securely check customer order status, payment state, fulfillment progress, and courier tracking details by order ID/number and matching customer email or phone.

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_or_number": "<order_id_or_number>",
      "customer_email_or_phone": "<customer_email_or_phone>"
    },
    "name": "check_order_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_id_or_numberYesOrder ID (e.g. ord_123) or Order Number (e.g. 4639)
customer_email_or_phoneYesCustomer email or phone number matching the order

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / customer_email_or_phone / description
      Previous value: -"Customer email or phone number matching the order [Required: non-empty valid value must be supplied]."New value: +"Customer email or phone number matching the order"
    • changedInput schema / properties / order_id_or_number / description
      Previous value: -"Order ID (e.g. ord_123) or Order Number (e.g. 4639) [Required: non-empty valid value must be supplied]."New value: +"Order ID (e.g. ord_123) or Order Number (e.g. 4639)"
  2. Changed2 schema fields changed
    • changedInput schema / properties / customer_email_or_phone / description
      Previous value: -"Customer email or phone number matching the order"New value: +"Customer email or phone number matching the order [Required: non-empty valid value must be supplied]."
    • changedInput schema / properties / order_id_or_number / description
      Previous value: -"Order ID (e.g. ord_123) or Order Number (e.g. 4639)"New value: +"Order ID (e.g. ord_123) or Order Number (e.g. 4639) [Required: non-empty valid value must be supplied]."
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It signals a security/verification requirement via 'Securely' and the matching-identifier pairing, but says nothing about what happens on failed verification, whether results are cached/delayed, or rate limits.

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?

A single front-loaded sentence that lists the returned facets and the identifier requirement with no filler. Every clause maps to a real decision the caller must make.

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 two-parameter read lookup with no output schema and no annotations, the description covers inputs, the verification requirement, and the scope of returned data. The main remaining gap is error/not-found behavior, which the agent would have to discover empirically.

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%, so both parameters are already fully documented, including their examples and the 'matching the order' constraint. The description's phrasing adds no syntax, format, or matching-rule detail beyond what the schema already states.

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?

States a specific verb ('check') and resource ('customer order status') and enumerates the sub-fields returned: payment state, fulfillment progress, courier tracking. The purpose is unmistakable and no sibling tool (cart, trade-in, club lookup) overlaps with it.

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?

The description embeds the key prerequisite: both an order ID/number AND a matching email or phone are needed, which tells the agent this is an identity-verified lookup rather than a free search. It does not state when to avoid the tool or what to do on a mismatch, so it stops short of full routing guidance.

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