Skip to main content
Glama

Shuttlely private charters

Ask for a written quote

request_quote
Idempotent

Routes from Vancouver, Calgary · Banff and Halifax, or anything custom: sends the request and Shuttlely emails a written per-vehicle price. No payment.

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": {
      "region": "<region>",
      "guests": "<guests>",
      "email": "<email>",
      "travellerConsent": "<travellerConsent>"
    },
    "name": "request_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesThe written quote is sent here
needsNoAnything the car or driver must allow for
phoneNoOptional phone number with country code
guestsYesGuests including children
regionYesDeparture city: toronto, vancouver, rockies (Calgary · Banff) or halifax
routesNoRoute slugs from that city (list_routes)
languageNoLanguage of the written quote email
agentNameNoWhich assistant or agent is asking, for the operator
requestIdNoGenerate once per request
startDateNoOmit if not decided
customRouteNoWhere else they want to go, in their words
travellerConsentYesTrue only after the traveller agreed to be contacted about this trip

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

The description excels at disclosing behavior beyond annotations by detailing the delivery mechanism ('Shuttlely emails a written per-vehicle price'). It clearly communicates that this is a non-transactional step with no payment requirement.

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?

The tool uses two concise sentences with no redundant phrasing. The primary function and scope are front-loaded, making it highly efficient for an AI agent to parse.

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

Completeness5/5

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

The tool is complex enough to warrant the behavioral detail provided. Since there is no output schema, the description successfully clarifies the result format (an email) and limitations (no payment), making it a complete definition for intent matching.

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?

Given that the schema description coverage is 100%, the description adds supplementary value rather than primary semantic information for the parameters. It adds operational context about how the request is processed and delivered.

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 clearly defines the action as requesting a 'written per-vehicle price' and specifies the geographical scope (Vancouver, Calgary, Halifax, custom). While it relates to obtaining a quote, it differentiates itself from 'place_order' by defining it as a request rather than a purchase.

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?

The description provides clear conditions for usage by listing the supported starting locations and confirming it works for 'anything custom.' The explicit statement 'No payment' acts as an important usage constraint.

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