Skip to main content
Glama

Pumpkin

update_rental_quote_details

Update eventName, venue, startsAt, endsAt, notes, contactPreference, or setup. Dates need an ISO offset. Enter contact details in the 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>",
      "revision": "<revision>",
      "mutationId": "<mutationId>",
      "details": "<details>"
    },
    "name": "update_rental_quote_details"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare a non-destructive, non-idempotent mutation with no open-world access, so safety is covered. The description adds a genuinely useful behavioral constraint (dates require an ISO offset) but says nothing about the meaning of revision/mutationId, concurrency/conflict behavior, or what happens on a stale revision — material for a mutation tool.

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 short sentences with no filler, front-loading the updatable field list before the format constraint. The final sentence about contact details is vague enough to be slightly misleading rather than helpful, which keeps it below a 5.

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?

This is a 5-required-parameter mutation with a nested `details` object, 20% schema coverage, and no output schema, so the description carries a heavy load. It omits revision/mutationId semantics, the accepted shape of `details`, and any statement of the result, leaving too much for the agent to infer.

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%, with just `site` documented, so the description must compensate. It does partially help by enumerating fields inside the opaque `details` nested object, but leaves site/draft/revision/mutationId, required keys of `details`, and whether the listed fields are optional entirely unexplained.

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?

Uses a specific verb ("Update") and names the concrete fields it can change (eventName, venue, startsAt, endsAt, notes, contactPreference, setup), so an agent knows the resource and scope without opening the schema. It does not distinguish itself from the sibling update_rental_quote_item, which is the main ambiguity for selection.

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 statement of when this tool should be used instead of update_rental_quote_item or add_rental_quote_item, and no prerequisites are given. The only quasi-guidance is the closing line about entering contact details in the form, which reads as a data-entry note rather than usage routing.

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