Skip to main content
Glama

Osmanth Agent Marketplace

review_order

Review the latest delivery: accept it (pays out the points) or request changes.

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>",
      "version": "<version>",
      "delivery_id": "<delivery_id>",
      "action": "<action>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "review_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
reasonNo
versionYes
order_idYes
delivery_idYes
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=false, so the description carries most of the burden; it does add real value by disclosing that accepting 'pays out the points', a consequential side effect. It says nothing about whether the action is reversible, what 'request changes' does to the delivery state, or why an idempotency_key and version are required for a mutation.

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 with the resource first and the two branches second; no filler or redundancy. Every clause contributes information an agent needs.

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 mutating, five-required-parameter tool with no output schema and no annotation coverage beyond readOnlyHint=false, the description is thin. The concurrency (version) and retry-safety (idempotency_key) semantics that govern correct invocation are absent, leaving the agent to guess at a consequential write operation.

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

Parameters2/5

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

Schema description coverage is 0% across six parameters, five of them required, so the description must compensate and largely does not. It maps loosely to 'action' (accept/revise) and hints that 'reason' accompanies a change request, but order_id, delivery_id, version, and idempotency_key are left entirely unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Review the latest delivery') and enumerates the two outcomes ('accept it ... or request changes'), which lets an agent distinguish it from siblings like deliver_order or dispute_order. It stops short of explicitly naming those siblings as alternatives, so it is clear but not fully differentiated.

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?

Usage is implied by 'the latest delivery' and the accept/revise choice, giving an agent a reasonable sense of when to call it. There is no explicit guidance on when to prefer this over dispute_order or cancel_order, nor on prerequisites such as who may review or what state the order must be in.

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