Skip to main content
Glama

search_trips

Search 3,900+ rail vacations (data version 8df5580ef8, prices last checked 2026-11-16) with plain words: destinations, named trains, months, budgets, durations, pace, comfort, 'no overnight trains'. Same parser as besttraintour.com/search.

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": {
      "query": "<query>"
    },
    "name": "search_trips"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesPlain-language search, e.g. 'two weeks in the alps under $5k, slow pace'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does add real value by disclosing corpus size (3,900+), the data version hash, and a 'prices last checked 2026-11-16' freshness caveat that tells the agent results may be stale. It says nothing about matching behavior (fuzzy vs strict), empty-result handling, or how limit truncates results.

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?

A single dense sentence that front-loads the corpus size and the plain-language query capability, with the external-parser note at the end. Nearly every clause earns its place, though the raw version hash '8df5580ef8' adds little for an invoking agent.

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

Completeness3/5

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

With no output schema and no annotations, the description should say more about what comes back: result shape, whether summaries or full itineraries, and how limit behaves. It covers the input side and freshness adequately, but the return contract and pagination behavior are left unspecified for a search tool.

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 50% and the description compensates well for the query parameter, giving concrete phrasings ('two weeks in the alps under $5k, slow pace', 'no overnight trains') that reveal it accepts natural-language constraints rather than keywords. The limit parameter has no schema description and is never mentioned, so half the surface remains undocumented.

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 a specific verb (search) and resource (3,900+ rail vacations) and enumerates the query dimensions it parses: destinations, named trains, months, budgets, durations, pace, comfort. An agent can tell this is the discovery entry point, though it never names get_trip or compare_trips as the follow-on tools.

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?

Usage is only implied: 'Search ... with plain words' suggests this is the first step of a find-then-inspect flow, and the sibling names compare_trips and get_trip hint at downstream steps. There is no explicit statement of when to use this instead of them, and no exclusion or prerequisite guidance.

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