Skip to main content
Glama

site

by uk.co.compressedairservicing
OverviewDiscussionsAdmin

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

submit_enquiry

Submits an enquiry to Compressed Air Servicing — 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: "Send my contact details to up to three compressed air service engineers, chosen by Compressed Air Servicing, who'll contact me directly. I'll be emailed each firm's name as my details go to it, and can stop any more firms getting them."

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
answersYesthe person's answers, keyed by field key
consentYestrue only when the person has agreed to: Send my contact details to up to three compressed air service engineers, chosen by Compressed Air Servicing, who'll contact me directly. I'll be emailed each firm's name as my details go to it, and can stop any more firms getting them.
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: Happy for my details to go to compressed air service engineers, who'll quote me directly."New value: +"true only when the person has agreed to: Send my contact details to up to three compressed air service engineers, chosen by Compressed Air Servicing, who'll contact me directly. I'll be emailed each firm's name as my details go to it, and can stop any more firms getting them."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and delivers: not a purchase/quote, server-side validation behavior, the returned artifacts, and the critical downstream gate that the person must click an emailed link before any provider sees the enquiry. Consent semantics are spelled out verbatim, removing ambiguity about what 'true' asserts.

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 and the not-a-purchase warning, then structured as numbered steps, which is easy to follow. The verbatim consent text is duplicated from the schema, a minor redundancy, but it is arguably needed for the agent to display it to the person.

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?

There is no output schema, and the description compensates by describing what step 1 returns (summary, consent line, confirmation token) and what step 2 triggers (submission plus a verification email). For a two-phase workflow tool, nothing an agent needs to execute it correctly is missing.

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 description coverage is 100%, so the baseline is 3, but the description adds real meaning: answers are keyed by field key sourced from enquiry_fields, consent must reflect a specific stated agreement, and confirmation is the token from step 1 and is only used on the second call. The gating semantics of the confirmation parameter go beyond the schema text.

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?

Specific verb (submits) plus resource (an enquiry to Compressed Air Servicing), with immediate disambiguation that it is NOT a purchase and NOT a guaranteed quote. The two-step framing and the reference to enquiry_fields clearly separate it from the sibling describe/fields tools.

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?

Explicitly enumerates Step 1 (with answers + consent=true, returns summary/consent line/token) and Step 2 (repeat only if the person agrees, with token). The condition gating each call is stated, so the agent knows exactly when to invoke which phase.

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