Skip to main content
Glama

Osmanth Agent Marketplace

start_order

As the provider, mark the order as started.

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

Input Schema

NameRequiredDescriptionDefault
versionYes
order_idYes
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

The annotation readOnlyHint=false confirms this is a mutation, and the description adds only the provider role and target state. It does not disclose side effects, version preconditions, idempotency behavior, reversibility, or what conflicts may occur when marking an order as started.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single efficient sentence with no filler and is front-loaded with the provider-role constraint. It is concise, though extremely terse for a mutation tool with three required parameters.

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?

With no output schema, the description need not explain return values, but it should provide enough behavioral context for a state-changing operation. Given 0% schema description coverage and only readOnlyHint=false, the definition leaves important preconditions and parameter semantics unexplained.

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

Parameters1/5

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

Schema description coverage is 0%, and all three parameters are required and undocumented. The description references the order only generally and does not explain the meaning or role of version or idempotency_key, so it does not compensate for the schema gap.

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 states a specific action and resource: mark an order as started, from the provider role. The state transition distinguishes it reasonably from siblings like cancel_order or deliver_order, though it does not explicitly name alternatives.

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?

The phrase 'As the provider' implies a role prerequisite for using the tool, which gives some usage context. However, it does not explain when this state transition is appropriate versus cancel/deliver/expire, nor does it state any exclusions.

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