Skip to main content
Glama

Confirm an enquiry

confirm_enquiry
Idempotent

Use this when the person has the 6-digit code from Bookatu's email about their enquiry and asks you to send it. The business replies to the person by email. Do not use for a held time: that is confirm_booking.

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": {
      "enquiryId": "<enquiryId>",
      "code": "<code>"
    },
    "name": "confirm_enquiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe 6-digit code from the email, as the person read it to you.
languageNoThe language to answer in (BCP 47).
enquiryIdYesThe enquiry id send_enquiry answered with.

Output Schema

NameRequiredDescriptionDefault
metaYes
enquiryYes
businessYes
nextStepYesWhat to tell the person next.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint false, destructiveHint false, idempotentHint true, openWorldHint true), so the description only needs to add what those don't cover. It does contribute the observable outcome ('The business replies to the person by email') and the provenance of the code, but it never says what confirmation actually changes on the enquiry or what happens when the code is wrong. Useful but partial beyond the structured hints.

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?

Three short sentences, front-loaded with the trigger condition and ending with the exclusion, with no filler. The pronoun 'it' in 'asks you to send it' is slightly ambiguous and costs a bit of clarity.

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?

An output schema exists, so return values need no explanation, and all parameters are fully documented in the schema. For a small, idempotent, non-destructive mutation the definition is nearly sufficient; only the side effect of confirming and error behavior for an invalid code are unstated.

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

Parameters3/5

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

Schema description coverage is 100%, so all three parameters including code and enquiryId are already documented, making 3 the baseline. The description reinforces that the code is a 6-digit value the person read aloud, which is mildly helpful for transcription, but adds nothing about language or enquiryId beyond the schema.

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

Purpose4/5

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

The description identifies the resource (an enquiry) and the operation (confirming it) via the required 6-digit code, and explicitly disambiguates from confirm_booking. It stops short of a single crisp verb+resource statement, since the action is framed indirectly as 'asks you to send it', leaving the reader to infer that the tool confirms the enquiry rather than merely sends a code.

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?

It states the precise trigger (the person has the 6-digit code from Bookatu's email about their enquiry) and an explicit exclusion with the correct alternative ('Do not use for a held time: that is confirm_booking'). An agent can route between the two confirmation tools without opening either schema.

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