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

Get Price Offer

get_price_offer

Retrieve a price offer for a specific train connection by providing the connection identifier and passenger details.

Instructions

Get a price offer for a specific connection. Note: Prices are already included in connection search results, so this separate endpoint is not available with the mobile API.

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": {
      "connectionId": "<connectionId>",
      "passengers": "<passengers>"
    },
    "name": "get_price_offer"
  }
}

Input Schema

Name	Required	Description	Default
`passengers`	Yes	Array of passenger types and counts
`connectionId`	Yes	Connection identifier from search results

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 11, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, and the description only notes that prices are included in search results. It does not disclose behavioral traits such as idempotency, error states, or requirements (e.g., valid connectionId).

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?

The description is concise with two sentences. The first sentence delivers the primary purpose, and the second provides relevant context. No superfluous information.

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?

For a simple tool with no output schema, the description covers the basic purpose and a usage caveat. However, it lacks details on expected return values or error conditions, leaving some gaps.

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%, meaning both parameters are described in the input schema. The description adds no extra meaning beyond what the schema already provides, meeting the baseline expectation.

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?

The description clearly states the action ('Get a price offer') and the target ('for a specific connection'). It is specific and unambiguous, but does not explicitly distinguish from sibling tools like get_connection_details or search_connections.

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 description mentions that prices are already in search results and that the endpoint is not available in the mobile API, implying when not to use it. However, it lacks explicit guidance on when to prefer this tool over alternatives.

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

Deploy Server