Skip to main content
Glama

Pumpkin

update_rental_quote_item

Set an existing rental cart line's quantity.

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>",
      "quantity": "<quantity>"
    },
    "name": "update_rental_quote_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesThe site ID returned by find_business.
draftYes
quantityYes
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 this is a non-read-only, non-destructive, non-idempotent, closed-world mutation. The description adds only that the target line must be "existing," which is modest context beyond the annotations. It says nothing about how revision conflicts are handled, what mutationId does for replay/deduplication, or what happens to the prior quantity value.

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 filler; the core action is stated immediately. It is arguably under-specified rather than bloated, but there is no wasted wording to trim.

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 six-parameter required mutation with no output schema and near-zero schema description coverage, the description does far too little: it never explains draft/revision/mutationId semantics, concurrency behavior, or the effect of overwriting a quantity. The only complete element is the action itself.

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 17% — just the site parameter is documented in the schema. Five of six required parameters (draft, revision, mutationId, variantId, quantity) carry no meaning anywhere, and the description only hints that quantity belongs to a cart line without explaining ranges, units, or how variantId/draft/revision identify the line.

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 ("Set") and a specific resource ("an existing rental cart line's quantity"), which lets an agent distinguish it from add_rental_quote_item or remove_rental_quote_item by the fact that it mutates an existing line rather than creating or deleting one. It stops short of naming any sibling, so differentiation is inferred rather than explicit.

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 tool versus update_rental_quote_details, add_rental_quote_item, or remove_rental_quote_item, and no stated preconditions such as needing an existing line or a current revision. The only implied usage is that the line must already exist, which is thin for a 6-required-parameter mutation.

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