Skip to main content
Glama

submitReview

Leave a FitsThis buyer review for a paid/shipped/delivered order. Requires orderId + the buyer email from PayPal checkout. One review per order. Use after getOrderStatus shows review.canSubmit.

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": {
      "orderId": "<orderId>",
      "email": "<email>",
      "rating": "<rating>",
      "body": "<body>"
    },
    "name": "submitReview"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesReview text, 10–2000 chars
emailYesBuyer email used at PayPal checkout
titleNo
ratingYes1–5 stars
orderIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose real behavioral context a schema can't: the order must be paid/shipped/delivered, the email must come from PayPal checkout, and there is a one-review-per-order cap. It omits what happens on rejection, whether the review publishes immediately or is moderated, and how the PayPal email is verified.

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?

Four short sentences, front-loaded with what the tool does, then requirements, then the ordering prerequisite. Every sentence adds a distinct constraint and none are wasted.

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 no-annotation, no-output-schema mutation tool with five parameters, the description covers the calling sequence, identity proof, eligibility state, and the one-per-order limit. It leaves the caller without guidance on the undocumented title parameter or on failure/duplicate handling.

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 60%, below the high-coverage baseline, so the description needs to compensate and only partly does. It explains orderId and that email is the PayPal checkout address, but that simply restates the schema's email description, and the entirely undocumented 'title' parameter is never mentioned at all.

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 verb and resource: 'Leave a FitsThis buyer review', with the eligible scope narrowed to paid/shipped/delivered orders. This clearly contrasts with getReviews-style read operations via the verb 'leave', but no sibling is named explicitly, so the differentiation is inferred rather than stated.

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?

It gives an explicit prerequisite chain — 'Use after getOrderStatus shows review.canSubmit' — plus the hard constraint 'One review per order' and the required identity inputs. There is no explicit when-not guidance (e.g. what to do when canSubmit is false, or how to handle a duplicate), which keeps it just short of a 5.

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