Skip to main content
Glama
Sign In
retail-order-sync-hub

retail-order-sync-hub

by JulioPradenas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

_trace_order

Trace an order's synchronization journey across webhooks, outbox pushes, and silver state to identify and resolve sync incidents.

Instructions

Return a cross-source timeline for an order: inbound webhooks → outbox pushes → silver state.

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

Input Schema

NameRequiredDescriptionDefault
order_idYes
api_tokenNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must convey behavioral traits. It states 'Return' implying read-only, but does not disclose permissions, rate limits, data freshness, or side effects. Minimal transparency for a read operation.

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?

The description is a single, well-structured sentence that conveys the core purpose without any extraneous words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having an output schema (not shown), the description does not explain the timeline content (e.g., timestamps, statuses) or how to interpret results. For a diagnostic tool, more detail is needed for completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description does not explain the parameters (order_id, api_token). The optional api_token role is unclear, and no format or usage guidance is given.

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 clearly states the tool returns a cross-source timeline for an order, listing specific sources (inbound webhooks, outbox pushes, silver state). This distinguishes it from sibling tools like _get_order_status (status only) and _find_failed_orders (finding failures).

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?

The description implies this tool is used for tracing order flows across sources, but it does not explicitly state when to use it versus alternatives, nor does it provide exclusions or prerequisites.

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