Skip to main content
Glama

Hop With Ann route finder

Find a route

find_route
Read-only

Island-hopping route from A to B in the Philippines: legs, usual departure times, notes and a pre-filled link for the traveller to request a quote. No prices, no live availability.

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

Input Schema

NameRequiredDescriptionDefault
toYesEnd place, e.g. "Siquijor", "Camiguin"
dateNoTravel date, YYYY-MM-DD (optional). At least 7 days ahead.
fromYesStart place, e.g. "Cebu City", "Panglao", "Mactan airport"
group_sizeNoNumber of travellers (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Adds substantial behavior beyond readOnlyHint and openWorldHint: it describes returned legs, usual departure times, notes, and a prefilled quote link, and explicitly says prices and live availability are absent. It does not cover failure modes or whether date and group_size affect leg selection, but the core behavioral profile is clear.

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?

Two sentences, front-loaded with the route scope and followed by output and limitation details; there is no filler. It is dense but efficient and every clause earns its place.

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 read-only lookup tool with no output schema, the description supplies the returned content and the key non-live and non-priced caveat, while the schema covers all four inputs. The missing sibling-selection guidance is a real gap, but within the tool's own scope the definition is essentially complete.

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 100%, so from, to, date, and group_size are already documented in the schema. The description adds only domain context (Philippine island-hopping, A-to-B routing) and does not explain parameter effects like the 7-day lead time beyond what the schema already says.

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?

States an A-to-B island-hopping route in the Philippines and enumerates what comes back: legs, usual departure times, notes, and a prefilled quote link. It also carves out non-capabilities (prices, live availability), which helps separate it from a generic route list, though it does not name list_routes or send_enquiry.

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

Usage Guidelines3/5

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

Implies use for planning an itinerary between two Philippine places and warns that it is unsuitable for pricing or live availability checks. It does not explicitly say when to choose list_routes or when to hand off to send_enquiry, so sibling routing must be 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