Skip to main content
Glama
Sign In

site

by com.sendaparcelcompare
OverviewDiscussionsAdmin

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

submit_enquiry

Submits an enquiry to Send A Parcel 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 Send A Parcel 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 Send A Parcel 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 Send A Parcel Compare shares your details with parcel carriers and booking brokers who may contact you with a price."New value: +"true only when the person has agreed to: By sending this you agree the Send A Parcel Compare team reads your enquiry and replies by email. We do not pass it to anyone else."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

No annotations are supplied, so the description carries the full burden and does so: it discloses that step 1 only validates and returns a summary/consent line/token, that nothing is submitted until step 2, and that even then the person must click an emailed link before any provider sees the enquiry. The consent semantics are quoted verbatim, which is exactly the kind of side-effect disclosure a mutation tool needs.

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 disambiguation ('NOT a purchase') and then organized as Step 1 / Step 2, which suits the flow. Slightly long because the consent sentence is quoted in full and duplicates the consent parameter description in the schema.

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 two-step, consent-gated submission with a nested answers object and no output schema, the description covers the return shape of step 1, the gating condition for step 2, and the downstream email-verification consequence. An agent has everything needed to run the flow 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 would be 3, but the description adds real sequencing meaning: answers are keyed by field key from enquiry_fields, consent must be true at both steps, and confirmation is the token returned by step 1 after approval. The only gap is that it does not say whether the token is short-lived or reusable.

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 Send A Parcel Compare') and immediately delimits scope with 'NOT a purchase, NOT a guaranteed quote.' That framing separates it cleanly from sibling tools like enquiry_fields and dataset_* which read data rather than submit anything.

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?

Gives an explicit two-step procedure with the exact condition that gates step 2 ('only if the person agrees') and names what to show the person between steps. It also points to enquiry_fields as the source of the field keys, so the agent knows the prerequisite call.

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