Skip to main content
Glama

Shuttlely private charters

List Shuttlely routes

list_routes
Read-only

Private-charter routes by departure city (Toronto, Vancouver, Calgary · Banff, Halifax), with lengths and the from-price for Toronto routes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_routes"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage of route titles: en (default) or zh

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint=false, so the safety profile is covered. The description contributes the useful detail that results include lengths and that from-prices are only exposed for Toronto routes, but it says nothing about ordering, pagination, or how many routes come back.

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?

One compact sentence with the most important scoping information (departure cities) up front and no filler. The fragmentary phrasing slightly weakens readability but nothing is wasted.

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 listing tool with one fully documented parameter and no output schema, the description conveys both the data set and the shape of the returned attributes well enough to call it correctly. The only ambiguity is why pricing appears limited to Toronto routes.

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?

The single language parameter is fully documented in the schema (100% coverage) including the enum values and default. The description adds no further meaning about parameter behavior, so the baseline 3 applies.

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 names the resource (private-charter routes), the organizing dimension (departure city) with concrete examples, and the returned attributes (lengths, from-price for Toronto). It is clearly distinguishable from the quoting/ordering siblings, though it is written as a noun phrase rather than an explicit verb.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus get_quote or request_quote, and no preconditions or exclusions. Only an implicit browse-then-book flow can 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