Skip to main content
Glama

Moqway

Answer a ship-date extension

respond_to_ship_extension
Destructive

The supplier may ask once per order for up to 7 more days to ship (order.ship_extension with status 'open'). Approve to accept the new date, or reject to keep the original deadline; if the order then passes it, the buyer may cancel for a full refund. Ask the human unless their instructions already cover it. No answer within 48 hours counts as approval.

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>",
      "decision": "<decision>"
    },
    "name": "respond_to_ship_extension"
  }
}

Input Schema

NameRequiredDescriptionDefault
decisionYes
order_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

The annotations already flag this as destructive and non-idempotent, so the safety profile is covered. The description adds downstream consequences that the annotations do not: rejecting the extension means that if the order later misses the deadline, the buyer may cancel for a full refund, and silence is treated as approval after 48 hours. It does not say whether the decision can be reversed or repeated, nor what is returned, but for a tool with this annotation coverage, that gap is minor.

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 opening states the rule and the scope first, then explains the approve/reject choice, then consequences, then the escalation and timeout policy. Every sentence adds a distinct operational fact, with no restating of the name or title and no filler.

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 has only two parameters and no output schema, yet it carries real risk because the annotations mark it destructive. The description covers the trigger condition, the effect of each decision, the downstream consequence, the human-escalation policy, and the timeout default, which is everything needed to call it correctly.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must explain meaning, and it explains the 'decision' enum well by giving the effect of each value. 'order_id' is only implied through the reference to 'order.ship_extension', with no statement of where the ID comes from or what it represents, so the description does not fully make up for the missing schema coverage. The result is a solid explanation with one visible gap.

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 names the specific situation ('The supplier may ask once per order for up to 7 more days to ship') and the exact action ('Approve to accept the new date, or reject to keep the original deadline'), so what the tool acts on is clear. It cannot be confused with siblings such as cancel_order or confirm_receipt, because it only answers an open extension request. The description also names the data it operates on ('order.ship_extension with status open'), which gives a precise trigger.

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?

It states exactly what each choice does: approve accepts the new date, and reject keeps the original deadline. It also gives a default rule ('Ask the human unless their instructions already cover it') and timeout handling ('No answer within 48 hours counts as approval'). Because these conditions and alternatives are explicit, an agent does not need to infer when and how to use the tool.

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