Skip to main content
Glama

Pumpkin

submit_rental_quote

DestructiveIdempotent

Send the exact reviewed request into Leads. No reservation is made.

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>",
      "proof": "<proof>",
      "captchaToken": "<captchaToken>",
      "consent": "<consent>"
    },
    "name": "submit_rental_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesThe site ID returned by find_business.
proofYes
consentYes
captchaTokenYes

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 destructiveHint=true, openWorldHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is largely pre-supplied. The description adds real value by scoping the side effect — an outbound lead is created but no reservation is booked — yet it says nothing about required consent/captcha preconditions, whether a prior review token is mandatory, or what repeat submission does given idempotentHint=true.

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, front-loaded sentences with zero filler; the effect statement is placed immediately after the action. It is lean to the point of under-specification for a four-required-parameter write tool, but nothing is wasted.

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 destructive, open-world submission with four required parameters (including an undocumented captcha token and consent flag) and no output schema, the definition leaves major gaps: the dependency on a prior review artifact, what 'proof' contains, what is returned, and what happens on captcha or consent failure are all unaddressed.

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?

Only 25% schema description coverage (only 'site' is documented). The description supplies no meaning for 'proof', 'consent', or 'captchaToken', which are all required and opaque — an agent must guess whether 'proof' is a review token or captcha proof. With low coverage the description was expected to compensate and does not.

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?

The verb+resource is concrete: it 'sends' a 'reviewed request' into a system called Leads. The word 'reviewed' modestly signals the ordering after review_rental_quote, but no sibling is named and 'Leads' is unexplained jargon, so the agent gets the action but not a crisp differentiation.

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?

'the exact reviewed request' implies a prerequisite (review must happen first, contents must not be edited) and 'No reservation is made' rules out one likely misreading. However, there is no explicit statement of when to call this versus review_rental_quote or get_rental_quote, nor any precondition or failure guidance.

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