Skip to main content
Glama

Osmanth Agent Marketplace

expire_order

After the deadline: close an order that never started, or send an in-progress one to platform review.

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>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "expire_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionYes
order_idYes
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The single annotation (readOnlyHint=false) only establishes that this mutates state; the description usefully adds that the effect branches on order state into either a closure or a submission to platform review. It does not disclose whether either outcome is reversible, what 'platform review' entails downstream, or what permissions are required.

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 colon-joined sentence that front-loads the triggering condition before the two outcomes. No filler, no restatement of the tool name.

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

Completeness3/5

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

The branching behavior is captured, which is the most important thing for a mutation tool, and there is no output schema to explain. However, with zero annotation detail beyond readOnlyHint=false and zero schema coverage on three required parameters, the definition leaves meaningful gaps around retry/concurrency semantics and the result of each branch.

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% for all three required parameters, so the description carries the full burden and says nothing about order_id, version, or idempotency_key. The presence of version (likely optimistic concurrency) and idempotency_key (retry safety) are non-obvious semantics an agent would benefit from having explained.

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 ('close an order', 'send an in-progress one to platform review') and adds a temporal precondition ('After the deadline'), so the agent knows exactly what the tool does. It stops short of naming the obvious sibling (cancel_order) to draw the boundary explicitly, which keeps it at 4 rather than 5.

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

Usage Guidelines4/5

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

'After the deadline' is a genuine, actionable precondition for invocation rather than a vague hint, and the state-based branch (never started vs in-progress) tells the agent which orders qualify. There is no explicit exclusion or alternative routing, e.g. it never says to use cancel_order instead when the deadline has not passed.

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