WaitApp

Rate a delivered order

rate_order

Idempotent

Leave a rating for the connected person's own DELIVERED order: food quality, delivery speed and packaging, each 1 to 5, an optional short comment, and optionally a rating for the rider. One rating per order; a repeat returns the existing one. The scores are the person's own. If the connection is set to confirm each decision, the first call returns the scores and submits nothing until a call with confirmed: true.

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": {
      "food": "<food>",
      "deliverySpeed": "<deliverySpeed>",
      "packaging": "<packaging>"
    },
    "name": "rate_order"
  }
}

Input Schema

Name	Required	Description
`food`	Yes
`comment`	No
`orderId`	No	The orderId from list_my_orders
`confirmed`	No	True records that the person agreed to submit these scores
`orderCode`	No	The order code returned when the order was placed, e.g. WA-K4M2
`packaging`	Yes
`riderRating`	No
`restaurantId`	No	The venue the order was placed at (needed with orderCode if the person has the same code at two venues)
`deliverySpeed`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 17, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations. Annotations declare a non-read-only, idempotent, non-destructive write; the description explains why it is idempotent (one rating per order, repeats return the existing one) and discloses the two-phase confirmation behavior where the first call returns scores but submits nothing. That is exactly the extra behavioral context a mutation tool needs.

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?

Three tight sentences, front-loaded with the action and its eligibility constraint, then the rating fields, then the idempotency and confirmation rules. 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?

With no output schema, the description carries the return-behavior burden and does so for the confirmation case (first call returns the scores). For a 9-parameter mutation tool it is nearly complete, though the identifier parameters (orderId vs orderCode vs restaurantId) are left to the schema.

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?

Schema coverage is only 44%, and the description helpfully compensates for the undocumented fields: it defines food/deliverySpeed/packaging as 1-5 scores, comment as optional and short, riderRating as optional, and explains what confirmed: true does. It does not clarify the relationship between orderId, orderCode and restaurantId, which the schema partially handles.

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 (rate) and resource (an order), plus the qualifying constraints: it must be the connected person's own and must be DELIVERED. It also enumerates the rated dimensions, so an agent can distinguish this from sibling tools like track_order or confirm_delivery_order without opening the schema.

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 operative context: one rating per order, a repeat returns the existing one, and the confirm-each-decision flow requires a follow-up call with confirmed: true. It does not name an alternative tool or an explicit when-not-to-use condition, but no sibling overlaps this action.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All WaitApp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?