Skip to main content
Glama

Pumpkin

remove_rental_quote_item

Remove a variant from the rental cart.

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>",
      "revision": "<revision>",
      "mutationId": "<mutationId>",
      "variantId": "<variantId>"
    },
    "name": "remove_rental_quote_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesThe site ID returned by find_business.
draftYes
revisionYes
variantIdYes
mutationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds only that the removal targets a rental cart, and says nothing about how draft/revision/mutationId participate in concurrency, whether the revision advances, or what happens on a stale revision — which matters because idempotentHint=false.

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?

A single front-loaded sentence with no wasted words. Brevity is not the problem here; the issue is that too little was said, not that it is padded.

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

Completeness2/5

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

For a 5-required-parameter mutation with no output schema and low schema coverage, the description should at least identify what draft, revision, and mutationId are for and what a caller gets back. None of that is present, leaving the agent to guess at concurrency semantics.

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 description coverage is only 20% (only 'site' is documented). The description hints that 'variant' maps to variantId, but leaves draft, revision, and mutationId entirely unexplained in both schema and description, which is a significant gap for 5 required parameters.

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?

States a specific verb ('Remove') and resource ('a variant from the rental cart'), so the operation is unambiguous. It does not differentiate itself from the sibling add_rental_quote_item / update_rental_quote_item beyond the verb, but the verb is distinct enough to be actionable.

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?

There is no guidance on when to use this versus update_rental_quote_item (e.g., setting quantity to zero) or add_rental_quote_item, and no mention of prerequisites such as needing an open draft. Usage is only implied by the tool name.

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