get_more_connectionsLoad earlier or later train connections for a previous search. Use the collection ID from search_connections results.
| Name | Required | Description | Default |
|---|---|---|---|
| direction | Yes | "next" for later trains, "previous" for earlier trains | |
| collection_id | Yes | Collection ID from search_connections results |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds context about pagination (earlier/later) but does not disclose additional behaviors like error handling or return format.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences, front-loaded with the core purpose and immediate usage hint. Every word earns its place, with no fluff or repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple pagination tool with rich annotations and complete schema, the description is sufficient. It lacks an explicit note about return structure, but that is implied as consistent with search_connections results, and the sibling tools provide context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, with both parameters (collection_id and direction) well-described in the schema. The description reinforces the source of collection_id but adds no new information beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Load' and resource 'earlier or later train connections' for a previous search, distinguishing it from sibling tools like search_connections (which performs the initial search) and get_prices/get_trip_details (which retrieve other data).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly says to use the collection ID from search_connections results, indicating the tool is a follow-up for pagination. It doesn't explicitly state when not to use other alternatives, but the context is clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct role: station search, connection search, pagination of results, trip details, pricing, and ticket purchase. There is no overlap that would confuse an agent; the only similar pair (search_connections and get_more_connections) is explicitly separated as initial search vs. loading more results.
All tool names follow a consistent verb_noun pattern (search_* for discovery, get_* for retrieval). The naming style is uniform and predictable, with no mixing of conventions or vague verbs.
With 6 tools, the server is well-scoped for its purpose: searching stations, planning connections, viewing details, checking prices, and buying tickets. Each tool earns its place, and the count is neither too thin nor bloated.
The tool set covers the complete user journey from station lookup and connection search to trip details, pricing, and direct ticket purchase. The workflow has no dead ends; after a search, trip IDs link seamlessly to downstream tools like get_prices and get_ticket_link.