Skip to main content
Glama

Shuttlely private charters

Book a Toronto trip

place_order
Idempotent

Submits an order for the traveller with their consent. No payment is taken: Shuttlely confirms availability by email, then sends a deposit link. Returns an order number.

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": {
      "trip": "<trip>",
      "traveller": "<traveller>",
      "travellerConsent": "<travellerConsent>"
    },
    "name": "place_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
tripYesThe same trip that was priced with get_quote
agentNameNoWhich assistant or agent is booking, for the operator
requestIdNoGenerate once per order; resending the same id never creates a second order
travellerYesWho is travelling and where Shuttlely should write
travellerConsentYesTrue only after the traveller agreed to book and to https://shuttlely.ca/en/terms

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?

Annotations already declare openWorldHint, idempotentHint, and non-destructive, but the description adds real context they don't cover: no payment is taken, availability is confirmed by email, a deposit link follows, and an order number is returned. It does not restate the idempotency guarantee (that lives in the requestId schema), which is a minor omission rather than a contradiction.

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?

Three short sentences, front-loaded with the action and the consent condition, then the payment/confirmation flow, then the return value. Nothing is redundant and no sentence could be dropped without losing information.

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 complex nested-schema mutation with no output schema, the description covers the key unknowns: no charge at booking, the email/deposit follow-up, and the returned order number. The main gap is the absence of explicit routing to the sibling pricing tools, which matters given three related siblings.

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 every parameter including the nested trip, traveller, and consent objects is already documented in the schema. The description only reinforces the consent requirement and adds no syntax, format, or constraint detail beyond what the schema provides, 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?

"Submits an order for the traveller with their consent" gives a specific verb (submits) and resource (order), and the title plus the no-payment note make clear this is the booking step rather than a pricing step. It stops short of naming get_quote or request_quote as the alternatives, so the differentiation is implied rather than stated.

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?

The consent precondition ("with their consent") and the note that no payment is taken imply this is the step after pricing, but the description never says when to use this versus get_quote or request_quote. An agent must infer the ordering from the schema's "The same trip that was priced with get_quote" note rather than from the description.

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