Skip to main content
Glama

site

by uk.co.eventhirecosts

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

submit_enquiry

Submits an enquiry to Event Hire Costs — 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: "Happy for my details to go to relevant event hire suppliers, who'll contact me directly with quotes."

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
answersYesthe person's answers, keyed by field key
consentYestrue only when the person has agreed to: Happy for my details to go to relevant event hire suppliers, who'll contact me directly with quotes.
confirmationNothe confirmation token from step 1, after the person has approved the summary

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden and meets it thoroughly. It discloses that step 1 only validates and returns artifacts, that step 2 actually submits the enquiry, and that the enquiry is not sent to providers until the person clicks the emailed link. It also states the exact consent wording, making behavioral expectations fully transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but densely informative, with each sentence serving a distinct operational purpose. It front-loads the most critical caveat ('NOT a purchase, NOT a guaranteed quote') and logically sequences the two steps without wasted words.

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?

With no output schema, the description fully compensates by explaining what step 1 returns (summary, consent line, confirmation token) and what happens after step 2 (email with a link, provider visibility only after click). The agent has enough context to execute the workflow correctly and manage the user's expectations.

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

Parameters5/5

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

Even though schema coverage is 100%, the description adds essential semantics beyond the schema: answers are keyed by field keys from enquiry_fields, confirmation is the token returned in step 1, and consent has an exact quoted meaning. This helps the agent correctly populate and sequence the parameters.

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?

The description states a specific action ('Submits an enquiry to Event Hire Costs') and immediately disambiguates from a purchase or guaranteed quote. It also clearly identifies the two-step nature of the tool, so an agent understands exactly what the tool accomplishes and what it does not.

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 description provides an explicit two-step usage protocol: call first with answers and consent=true to get a summary and confirmation token, then call again with the same answers plus the token only if the person agrees. It also specifies the consent condition and the email-link requirement, giving clear when-to-invoke guidance.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: enquiry_describe provides the conceptual overview, enquiry_fields provides the schema, and submit_enquiry performs the actual submission. No two tools could reasonably be confused for one another.

Naming Consistency3/5

The naming is readable and consistently lowercase with underscores, but the grammatical pattern is mixed: enquiry_describe and enquiry_fields are noun-first, while submit_enquiry is verb-first. This inconsistency is minor and does not significantly harm usability.

Tool Count5/5

Three tools is ideal for this narrow, single-workflow server. Each tool covers a necessary part of the enquiry process without redundancy or bloat.

Completeness5/5

The server fully covers the intended workflow: orienting the user, discovering required fields, and submitting an enquiry with a two-step confirmation token. There are no obvious dead ends or missing operations for the stated purpose.

Resources