bitroad-mcp

Seller attach tracking

seller_attach_tracking

Idempotent

Attach or update tracking information for a shipped order using order ID, carrier, and tracking number, replacing any previous tracking details.

Instructions

Attach or update tracking on an already-shipped order. Use mark_shipped for first ship; this is for late-arriving tracking only.

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>",
      "carrier": "<carrier>",
      "tracking_number": "<tracking_number>"
    },
    "name": "seller_attach_tracking"
  }
}

Input Schema

Name	Required	Description
`carrier`	Yes	Carrier handling the shipment.
`order_id`	Yes	UUID of the order to attach tracking to (must be awaiting fulfilment or shipped).
`tracking_number`	Yes	Carrier tracking number; replaces any tracking already on the shipment.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 8, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds minimal behavioral context beyond the annotations, such as noting it 'attaches or updates' tracking, but does not describe side effects or auth requirements beyond what the schema already provides. The schema covers replacement of existing tracking, so the description adds little extra transparency.

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 two sentences with no wasted words. The purpose is front-loaded, and the usage guidance follows immediately. It is concise and well-structured.

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

Completeness5/5

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

The tool is simple with three parameters and no output schema. The description covers purpose and usage, the schema covers parameters, and annotations cover idempotency and destructive behavior. Nothing essential for an agent to call this tool correctly is missing.

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?

The input schema has 100% description coverage for all three parameters, so the schema already documents each parameter's meaning. The description does not add parameter-specific semantics, but the purpose statement helps contextualize why these parameters are needed. With full schema coverage, the baseline of 3 is appropriate.

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 states a specific verb ('Attach or update'), a specific resource ('tracking on an already-shipped order'), and explicitly distinguishes from the sibling mark_shipped by noting this is for late-arriving tracking only. This makes the tool's purpose clear and differentiates it from similar tools.

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

Usage Guidelines5/5

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

The description explicitly instructs when to use this tool versus the alternative: 'Use mark_shipped for first ship; this is for late-arriving tracking only.' This is direct and unambiguous guidance.

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

Deploy Server