Skip to main content
Glama
Sign In
mcp-cha-cha

mcp-cha-cha

by danny-sbr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

pickup_order

Mark an order as picked up to update its status once the customer collects it.

Instructions

標記訂單為已領取

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

Input Schema

NameRequiredDescriptionDefault
order_idYes訂單 ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of explaining behavior. It states the core state transition but does not disclose side effects, whether the operation is idempotent, what happens if the order is already picked up, or any authorization requirements.

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, direct sentence with no filler. The verb and the object are front-loaded, making the purpose immediately clear.

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?

For a state-changing tool with no annotations and no output schema, the description is too thin. It provides no information about required preconditions, error cases, or the response after a successful pickup, leaving important operational context to speculation.

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 only parameter, order_id, is documented as '訂單 ID'. The description adds no additional meaning beyond the schema, so the baseline 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, '標記訂單為已領取' ('Mark order as picked up'), states a specific verb (mark) and resource (order) with a clear resulting state. It is naturally distinct from siblings like create_order, cancel_order, and get_orders.

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

Usage Guidelines2/5

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

The description gives no guidance about when to use this tool versus create_order, cancel_order, or get_orders. Prerequisites such as the order needing to exist or be in a certain status are not mentioned, so the agent has to infer usage from the tool name alone.

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