Skip to main content
Glama

Pumpkin

rental_get

Read-only

Read an eligible rental item, its pictures, contents, and setup requirements.

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

Input Schema

NameRequiredDescriptionDefault
siteYesThe site ID returned by find_business.
variantIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds value by enumerating what is returned (pictures, contents, setup requirements), but leaves the 'eligible' precondition and the non-idempotent read hint unexplained.

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, and the return contents are listed efficiently. It is terse to the point of under-specification, but nothing is wasted.

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?

With no output schema, the description does partially cover return values, which is the right instinct. However, it omits the eligibility precondition, the meaning of variantId, and any failure behavior for an ineligible item, which leaves real gaps for a two-required-parameter lookup.

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 in the schema as coming from find_business, while 'variantId' has no description anywhere. The prose adds nothing about either parameter, so it fails to compensate for the undocumented variantId and its relationship to the site.

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 (Read) and resource (rental item) plus the payload an agent can expect back (pictures, contents, setup requirements). That distinguishes it reasonably from siblings like rental_search and get_rental_quote, though it never explicitly names a counterpart.

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 when-to-use guidance, no stated alternative (e.g. rental_search to find an item first, get_rental_quote for pricing), and no explanation of what 'eligible' means or what makes an item ineligible. The only implicit cue is the word 'eligible', which the agent must guess at.

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