Skip to main content
Glama

Pumpkin

review_rental_quote

Open review for the current rental cart and form.

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": {
      "site": "<site>",
      "draft": "<draft>"
    },
    "name": "review_rental_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesThe site ID returned by find_business.
draftYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world operation, so the agent knows it mutates state. The description adds nothing about what state is created, whether repeated calls produce duplicate review sessions (consistent with idempotentHint=false), or what is required before calling. For a state-changing tool with a bare one-line description, that is a significant disclosure gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded with no filler, but it is under-specified rather than concise — it is too short for the complexity implied by a mutating two-parameter workflow tool. There is no structure beyond one clause.

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

Completeness1/5

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

A non-idempotent mutation tool with two required parameters, one undocumented and no output schema, receives no side-effect, sequencing, or return-value context. Given the complexity and thin structured support, the description is materially inadequate for correct invocation.

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 coverage is only 50%: `site` is documented as the ID from find_business, but `draft` is an opaque 100-character string with no schema description at all. The description supplies no meaning for either parameter, so it fails to compensate for the uncovered `draft` argument, leaving the agent unable to know what value to supply.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Open review for the current rental cart and form" gives a verb (open) and an object (rental cart review/form), so a reader can guess it begins some review step for the quote in progress. But it never says what a "review" is, what is opened, or how it differs from siblings like submit_rental_quote, get_rental_quote, or public_request_review. The purpose is inferable 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 Guidelines2/5

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

No when-to-use condition, no prerequisites (e.g. cart must contain items), and no mention of alternatives such as submit_rental_quote or public_request_review. The agent must guess where this fits in the quote lifecycle.

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