Czech Railways (České dráhy) MCP Server

Get Connection Details

get_connection_details

Retrieve detailed information about a specific train connection using its handle and identifier from search results.

Instructions

Get detailed information about a specific train connection. Note: This endpoint is not available with the mobile API - all connection details are included in search results.

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": {
      "handle": "<handle>",
      "connectionId": "<connectionId>"
    },
    "name": "get_connection_details"
  }
}

Input Schema

Name	Required	Description	Default
`handle`	Yes	Connection search handle from a previous search
`connectionId`	Yes	Connection identifier from the search results

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 11, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the mobile API limitation but does not mention auth, rate limits, or non-destructive nature. The 'get' verb implies read-only, which is adequate but not explicit.

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?

Two sentences: first states the purpose, second adds a crucial usage note. No wasted words, front-loaded, and to the point.

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?

The description covers the tool's purpose and a key limitation, but lacks details on what 'detailed information' includes (e.g., stops, prices). With no output schema, more context on return content would be helpful, though not critical for a simple 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 100% and both parameters (handle, connectionId) are well-described in the schema. The description adds no extra parameter meaning, which is acceptable given the schema covers it.

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 clearly states it gets detailed information about a specific train connection, distinguishing it from sibling search_connections which lists connections. The note about mobile API adds specificity.

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 explicitly says to get details of a specific connection and notes it is not available with the mobile API, implying use search_connections instead. This provides clear context but lacks an explicit alternative mention.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server