Skip to main content
Glama
Sign In

site

by com.equipmentrentalcompare
OverviewDiscussionsAdmin

Submit an ENQUIRY to human providers (two steps; not a purchase)

submit_enquiry

Submits an enquiry to Equipment Rental Compare: NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a confirmation token; show the person the summary and the consent line. Step 2: only if the person agrees, call again with the same answers, consent=true and the confirmation token; the enquiry is then submitted, and the person receives an email with a link they must click before any provider sees it. Consent means the person has read and agreed to: "By sending this you agree the Equipment Rental Compare team reads your enquiry and replies by email. We do not pass it to anyone else."

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": {
      "answers": "<answers>",
      "consent": "<consent>"
    },
    "name": "submit_enquiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
answersYesthe person's answers, keyed by field key
consentYestrue only when the person has agreed to: By sending this you agree the Equipment Rental Compare team reads your enquiry and replies by email. We do not pass it to anyone else.
confirmationNothe confirmation token from step 1, after the person has approved the summary

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / consent / description
      Previous value: -"true only when the person has agreed to: By submitting you agree Equipment Rental Compare passes your details to rental companies covering your area."New value: +"true only when the person has agreed to: By sending this you agree the Equipment Rental Compare team reads your enquiry and replies by email. We do not pass it to anyone else."
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does most of it: validation on step 1, non-committal nature of the call, a double opt-in email link before any provider sees it, and an explicit definition of what consent means. The gaps are error behavior (what happens with invalid answers) and duplicate/resubmission handling, which are not covered.

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?

Front-loaded with the purpose qualifier, then cleanly split into Step 1 and Step 2, which mirrors the call pattern. The verbatim consent sentence is long and is also duplicated in the schema's consent description, so there is some redundancy, though it is arguably load-bearing for correct consent handling.

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

Completeness5/5

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

For a nested-object, no-output-schema, no-annotation mutation tool, the description covers what step 1 returns (summary, consent line, token) and what side effect step 2 has (email requiring a click before provider visibility). An agent has enough to drive both calls correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description earns above that by explaining that answers are keyed by field key sourced from enquiry_fields and that confirmation is the token returned in step 1 rather than an independent value. It still does not describe the expected value shapes or which keys are mandatory within the answers object.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Submits an enquiry to Equipment Rental Compare") and immediately bounds it with two explicit negatives ("NOT a purchase, NOT a guaranteed quote"). It also names the related source of field keys (enquiry_fields), so an agent can separate this from the data/dataset siblings without opening a schema.

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

Usage Guidelines5/5

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

The two-step protocol is spelled out with an explicit gate: step 1 always, step 2 "only if the person agrees." It also states what to do with step 1's output ("show the person the summary and the consent line") and which fields to resend, leaving no sequencing ambiguity.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All site toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources