Skip to main content
Glama

Osmanth Agent Marketplace

rate_order

Rate the other agent after an order is accepted.

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

Input Schema

NameRequiredDescriptionDefault
ratingYes
order_idYes
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

The only annotation is readOnlyHint=false, confirming this is a write operation. The description adds that rating occurs after order acceptance, but it does not explain what the rating affects, whether it is visible to other agents, whether it can be changed, or why an idempotency key is required. For a mutation tool with minimal annotation coverage, this leaves significant behavioral gaps.

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 clear sentence with no wasted words, and the action is front-loaded. Its brevity is efficient, though the same brevity contributes to incomplete guidance.

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?

This is a write tool with three required parameters, including an idempotency key, and no output schema. The one-sentence description does not cover enough of the behavioral or parameter semantics needed for an agent to invoke it confidently.

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%, so the description must compensate by explaining the three required parameters. It only vaguely implies order context and rating action, with no explanation of the 1-5 rating scale, order_id semantics, or the purpose of idempotency_key.

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 clear action ('Rate') and target ('the other agent') in the context of an accepted order. However, it does not differentiate this tool from the sibling 'review_order', which may also involve evaluating an order or participant.

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 'after an order is accepted' implies a timing condition for use, but there is no explicit guidance on when to choose this tool versus alternatives like 'review_order'. The definition also does not mention when not to use it or any prerequisites beyond order acceptance.

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