Skip to main content
Glama

Send an enquiry

send_enquiry
Idempotent

Use this when a person wants to ask a business on Bookatu about a trip or service, or ask it a question, instead of holding a time. Pass the person's own words as message, and people or dates only if they said them. Bookatu emails the person a 6-digit code and a link, and nothing reaches the business until they confirm. Do not use for booking a time that check_availability offers, or for health details.

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": {
      "business": "<business>",
      "client": "<client>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "send_enquiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientYes
peopleNoHow many people, only if the person said so.
messageNoThe person's own words, as they said them.
businessYesThe business: its bookatu.com link or its own domain on Bookatu, or its slug.
languageNoThe language to answer in (BCP 47).
serviceIdNoA service or trip from list_services. Leave it out for a general question.
preferredEndNoThe last day the person said, YYYY-MM-DD, on or after the first day.
idempotencyKeyYesThe same key and the same details for a retry of one enquiry; a new key for anything else.
preferredStartNoThe first day the person said, YYYY-MM-DD.

Output Schema

NameRequiredDescriptionDefault
metaYes
sentToYesThe address the email goes to, masked.
enquiryYes
serviceYes
businessYes
demoCodeNoThe demo business only: the code to confirm with.
nextStepYesWhat to tell the person next.
bookingPageUrlYesWhere the person can send it on the business's own page.
demoConfirmUrlNoThe demo business only, for an example address that gets no email: the link the email would have carried. The person opens it to send the enquiry.
nextStepIfNoEmailNoWhile the enquiry waits: what to do if the person has no email after a few minutes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / demoConfirmUrl
      Added value: +{
      +  "description": "The demo business only, for an example address that gets no email: the link the email would have carried. The person opens it to send the enquiry.",
      +  "type": "string"
      +}
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true, idempotentHint=true and destructiveHint=false, but the description adds the crucial workflow context those hints cannot convey: Bookatu emails a 6-digit code and link, and nothing reaches the business until the person confirms. That double opt-in gate is the single most important behavioral fact about this tool. It stops just short of explaining retry/idempotency behaviour or what a failed confirmation means.

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?

Four tight sentences, front-loaded with the selection rule, then the input rule, then the mechanism, then the exclusion. Some redundancy with the schema ('Pass the person's own words as message' restates the message field description), which costs a little, but nothing is padded.

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

Completeness4/5

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

With 9 parameters, a nested client object, an output schema and rich annotations, the description covers what an agent most needs: when to route here, what not to invent, and that the enquiry is inert until confirmed. Gaps are minor — it never mentions the language parameter or how this hands off to confirm_enquiry by name.

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 89%, so the baseline is 3 and the schema already documents each field including 'only if the person said so'. The description adds a real constraint beyond field definitions: pass the person's own words as message, and people or dates only if they said them — an anti-fabrication rule that governs three parameters at once. It does not mention language or serviceId, so it is not fully additive.

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 ('ask a business on Bookatu about a trip or service, or ask it a question') and immediately frames it against the alternative action of 'holding a time', which maps onto the hold_booking sibling. An agent can distinguish this from check_availability or hold_booking without opening any 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?

Gives explicit when-to-use ('a person wants to ask a business... instead of holding a time') and explicit when-not-to-use ('Do not use for booking a time that check_availability offers, or for health details'), naming the sibling that should be used instead. Exclusions are concrete, not inferred.

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