Skip to main content
Glama

Hop With Ann route finder

Send a trip enquiry to Ann

send_enquiry

Send the traveller's trip plan to Ann for a free quote. ONLY use after the traveller has clearly agreed to share their name and contact details with Hop With Ann. Ann replies within 24 hours (usually the same day) by email or WhatsApp. This does not book or charge anything.

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": {
      "traveller_consent": "<traveller_consent>",
      "name": "<name>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "send_enquiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesTrip end, e.g. "Siquijor"
fromYesTrip start, e.g. "Cebu City"
nameYesTraveller name
emailNoEmail (email or WhatsApp needed)
countryNoWhere the traveller is from (optional)
messageNoAnything else: hotels, flight times, children, luggage, special needs
end_dateNoYYYY-MM-DD (optional)
reply_byNoHow the traveller wants Ann to reply
whatsappNoWhatsApp number with country code, e.g. +44 7700 900123
assistantNoName of the AI assistant sending this, e.g. "ChatGPT"
group_sizeNo
start_dateNoYYYY-MM-DD (optional)
extra_stopsNoStops in between, in order (optional)
traveller_consentYestrue only if the traveller has explicitly agreed to send their details to Hop With Ann

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so the description doesn't need to re-state safety. It adds real context beyond them anyway: a 24-hour (usually same-day) reply over email or WhatsApp, and that nothing is booked or charged. It leaves out what happens on resend (idempotentHint=false) and what a failed send looks like, which keeps it short of a 5.

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?

Four short sentences, front-loaded with the action and the consent gate before the softer details about response time and cost. Nothing is repeated from the title and no sentence is filler.

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?

For a 14-parameter, no-output-schema submission tool, the description covers what is sent, to whom, under what consent, what the reply channel and timing are, and that no booking or charge occurs. The remaining gap is failure and duplicate-send behavior, which matters given idempotentHint=false.

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 coverage is 93%, so the 14 parameters are already documented individually and this is baseline territory. The description reinforces the one non-obvious requirement, that the traveller has explicitly consented and that name plus contact details are being shared, which gives the required traveller_consent flag operational meaning. It doesn't explain the reply_by / email / whatsapp interaction beyond what the schema says.

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 object ("Send the traveller's trip plan to Ann") plus the outcome ("for a free quote"). That is clearly distinct from the sibling route-search tools, so an agent can select it without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a hard precondition in capitals ("ONLY use after the traveller has clearly agreed to share their name and contact details") and adds a scope exclusion ("does not book or charge anything"). It doesn't name a competing tool to use instead, but the condition that selects this tool is unambiguous.

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