Skip to main content
Glama

Rate an order

rate_order
DestructiveIdempotent

Records the customer's 1–5 star rating and optional comment for a delivered Fold order (rating again replaces the earlier one). Works with the connected account, or order code + the email used when scheduling. For a high rating the response includes Fold's public review link the customer may choose to use; for a low rating it notes that report_issue opens a support case (re-clean, damage, missing item).

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": {
      "orderCode": "<orderCode>",
      "stars": "<stars>"
    },
    "name": "rate_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoNot needed with a connected account.
starsYes
commentNoOptional, up to 500 characters, in the customer's words.
orderCodeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare destructive and idempotent hints, and the description earns credit by explaining the overwrite behavior (rating again replaces the earlier one) and the rating-dependent response content — the public review link versus the support-case note. It does not explain permissions or any rate limits, but with annotations present the bar is lower and this adds substantial context beyond them.

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?

Three tight sentences, front-loaded with the action and its scope before the auth and response details. Dense and nearly waste-free, though the parenthetical alternates (connected account vs. order code + email) are more compressed than ideal.

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

Completeness5/5

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

No output schema exists, so the description carries the return burden — and it does, describing the conditional response for high versus low ratings. Combined with the auth paths and overwrite semantics, an agent has everything needed to call it correctly.

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

Parameters3/5

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

Schema coverage is 50% (email and comment are documented; stars and orderCode are not). The description compensates partially by defining the 1–5 star scale, the optional free-text comment, and crucially the pairing rule — order code plus the email used when scheduling. That pairing is genuine value beyond the schema, but the meaning of orderCode itself is never spelled out, so it lands at baseline-plus rather than a 4.

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 a 1–5 star rating plus optional comment for a delivered Fold order — and immediately scopes what counts as eligible (delivered order). It also distinguishes the tool's own feedback path from the sibling report_issue, so an agent can tell it apart without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit routing: for a low rating the customer should be pointed at report_issue, which opens a support case for re-clean, damage, or missing item, while a high rating yields a public review link. It also states the two valid calling contexts (connected account, or order code + scheduling email), leaving little to inference.

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