Skip to main content
Glama

Pumpkin

get_rental_quote

Open or resume an editable quote-request form and cart. Staff prepares the final quote.

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

Input Schema

NameRequiredDescriptionDefault
siteYesThe site ID returned by find_business.
draftNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare this as a non-read-only, non-destructive, non-idempotent, closed-world operation, so the safety profile is covered. The description adds genuine context beyond that: the form and cart are 'editable' and the final quote is prepared by staff, clarifying that this call does not itself produce a binding quote — an important expectation for the agent. It does not explain repeat-call behavior, which matters given 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?

Two short sentences, front-loaded with the action and resource; the second sentence adds non-obvious context rather than filler. Slightly terse given the unresolved 'draft' parameter, but no wasted wording.

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

Completeness3/5

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

For a mutation-style tool with no output schema, the description should say what an 'open' yields (a quote identifier, a form URL, or a draft handle) so the agent knows how to pass it to sibling item tools. It also leaves the 'draft' semantics undefined. Adequate but with clear gaps.

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 50%: 'site' is well documented in the schema, but 'draft' has no description. The tool description never mentions either parameter and only vaguely hints at resumption, so it does not compensate for the undocumented 'draft' parameter or explain its format/role.

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 pair ('Open or resume') and a concrete resource ('editable quote-request form and cart'), which is more informative than the tool name alone. It is reasonably distinguishable from the item-level siblings (add_rental_quote_item, update_rental_quote_item) because it describes session/form creation rather than line-item editing, though it never explicitly contrasts with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

'Open or resume' implies the entry-point usage (start a new quote or return to an existing one), which is useful implied guidance. However, there is no explicit when-to-use vs. when-not, no mention that item-level tools should follow, and no stated prerequisites for the 'site' value beyond the schema.

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