Skip to main content
Glama

Pumpkin

rental_estimate

Read-only

Calculate an optional provisional estimate for the current cart and dates.

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": "rental_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesThe site ID returned by find_business.
draftYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows nothing is mutated; the description adds that the result is provisional and optional, i.e. not authoritative. It does not disclose whether the estimate is cached, how long it stays valid, or whether it requires a populated draft — useful context given the unusual readOnly + idempotentHint=false combination.

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 or repetition. It is efficient, though the qualifiers 'optional provisional' hedge slightly and the brevity leaves the important draft semantics unaddressed.

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 calculation tool with no output schema, so the description is the only place an agent can learn what the estimate returns — price breakdown, currency, or validity — and it says nothing about that. It also leaves the required 'draft' parameter undefined, which is a real gap for a tool that cannot be called without it.

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 string with no description. The phrase 'current cart and dates' hints that draft encodes cart and date context, yet the description never explains the draft format or where the 'dates' referenced actually live, leaving the second required parameter ambiguous.

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 and resource ('Calculate ... estimate') scoped to 'the current cart and dates', which tells an agent exactly what domain object is priced. It does not name or distinguish itself from the sibling service_estimate, so the boundary between rental and service pricing must be inferred.

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?

'Optional provisional' implies this is a non-binding, pre-quote calculation rather than a commitment, which is a real usage hint. However, it never says when to call it versus get_rental_quote, review_rental_quote, or the submit path, and gives no prerequisites (e.g. whether the cart must already contain items).

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