Skip to main content
Glama

Seatac Co trip planner

Seatac Co service info

get_service_info
Read-onlyIdempotent

Describe Seatac Co: private, pre-booked rides between Seatac Airport and the Seattle area, plus hourly charters. Returns the service area, vehicle types with passenger and bag capacity, booking requirements, and the cancellation and refund policy. Fares are quoted per trip; use quote_ride for a live price.

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": "get_service_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
bookingNo
businessNo
policiesNo
vehiclesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "booking": {
      +      "type": "object"
      +    },
      +    "business": {
      +      "type": "object"
      +    },
      +    "policies": {
      +      "type": "object"
      +    },
      +    "vehicles": {
      +      "type": "array"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, destructiveHint=false, so the safety profile is covered. The description adds useful behavior beyond that: the content is static reference material and fares here are quoted per trip rather than live, which explains why an agent must call quote_ride for pricing — a real operational constraint.

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 sentences, front-loaded with what the service is, then what the response contains, then the pricing caveat with the alternative named. No filler and no repetition of the title.

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?

For a zero-parameter, read-only info tool with an output schema, the description is complete: it names what will be returned and preempts the predictable confusion about pricing by pointing to quote_ride. Nothing needed to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters and the description correctly describes it as a parameterless lookup with no filtering options. With no parameters to explain, the baseline of 4 applies; nothing is misrepresented.

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?

The description uses a specific verb ("Describe") with a specific resource (Seatac Co: private pre-booked airport rides and hourly charters) and enumerates exactly what comes back — service area, vehicle types with capacity, booking requirements, cancellation/refund policy. An agent can immediately distinguish this from the transactional siblings like quote_ride and start_booking.

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?

It states the intended use implicitly (general service/policy reference before booking) and explicitly redirects pricing questions to quote_ride for a live price, which is a genuine routing cue. It stops short of saying when-not to use it (e.g., during an active booking flow) or naming other alternatives, so it is clear but not exhaustive.

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