Skip to main content
Glama

Moqway

Rate an order

rate_order
Idempotent

Records the buyer's rating of a shipped order, 1–5 stars: quality and as_described (goods match the photos and specs) are required, packaging and service optional. Only send ratings the buyer actually gave you; never guess them. Ratings feed Moqway's supplier rating and are not shown to the supplier. Calling again replaces the rating (allowed for 90 days after shipping).

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>",
      "quality": "<quality>",
      "as_described": "<as_described>"
    },
    "name": "rate_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentNo
qualityYes
serviceNo
order_idYes
packagingNo
as_describedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it discloses downstream effects (feeds Moqway's supplier rating), supplier visibility ('not shown to the supplier'), replacement semantics for repeat calls, and the 90-day mutation window. These are exactly the behavioral facts an agent cannot get from readOnlyHint/idempotentHint/destructiveHint, and none of them contradict those hints.

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 dense paragraph that front-loads the core action and required fields before moving to constraints and side effects. Every sentence contributes a distinct fact — requirements, grounding rule, privacy/effect, replacement window — with no filler.

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

Completeness4/5

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

For a 6-parameter mutation with no output schema, the definition covers requirements, validity window, effect on the supplier rating, and repeat-call behavior, which is close to complete. The remaining gaps are the purpose of the comment field and any hint about what the call returns or how failures (e.g., outside the 90-day window) surface.

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?

With 0% schema description coverage across 6 parameters, the description carries the load and does much of it: it identifies quality and as_described as required, packaging and service as optional, defines the 1–5 scale, and clarifies that as_described means goods match photos and specs. It leaves order_id and especially the free-text comment parameter unexplained, which is a real but modest 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?

States a specific verb and resource — 'Records the buyer's rating of a shipped order' — and immediately names the rating dimensions, so it is distinguishable from siblings like confirm_receipt or open_dispute. The scope ('shipped order', 1–5 stars) is precise enough that an agent knows exactly what action this performs.

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?

Gives clear conditions: the order must be shipped, the rating window is 90 days, and only ratings the buyer actually supplied should be sent ('never guess them'). It also explains re-invocation behavior (replaces the prior rating). It stops short of naming an alternative tool or an explicit when-not-to-use case, but no competing sibling for this action is evident.

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