Skip to main content
Glama

Pumpkin

rental_availability

Read-only

Check provisional availability for the current cart and event 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_availability"
  }
}

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 cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower, and the word "provisional" adds real value by signaling the answer is not a hold or guarantee. However, the description does not explain why a read-only check carries idempotentHint=false, nor what the response indicates, and it introduces "event dates" that have no corresponding input parameter.

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 key qualifier "provisional" appears early. It is efficient but borders on under-specification given the schema gap around "draft".

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 two-parameter, no-output-schema tool, the description leaves too much open: what "draft" is, where event dates come from, and whether the check returns a boolean, a list of options, or costs. An agent cannot construct a confident call or interpret the result from this definition alone.

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 but "draft" has no description in either the schema or the description. The description further muddies this by referring to "current cart" and "event dates" without tying either to a parameter, so it does not compensate for the undocumented required "draft" field.

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 ("Check provisional availability") and scopes it to the current cart and event dates, which separates it from pricing/orientation siblings like rental_estimate or rental_search. It stops short of naming any sibling it is explicitly not, so an agent must infer the boundary from the name alone.

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?

Usage is only implied: the phrase "current cart" hints that a populated cart must exist first, and "provisional" hints this is a pre-check before quoting. There is no explicit guidance on when to call this versus rental_estimate, rental_search, or review_rental_quote, and no statement of what to do with the result.

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