Skip to main content
Glama
Sign In
Czech Railways (České dráhy) MCP Server

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

by JanProvaznik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Passenger Types

get_passenger_types

Get available passenger types and discount categories for Czech Railways, such as adult, child, senior, and student, to select the correct fare for your journey.

Instructions

Get a list of available passenger types and discount categories (e.g., adult, child, senior, student discounts).

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_passenger_types"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided, so the description carries full burden for behavioral disclosure. It correctly implies a read operation but does not explicitly state safety, authentication needs, or latency. For a simple list tool, this is adequate but not thorough.

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?

The description is a single sentence that efficiently communicates the tool's purpose and includes specific examples. No superfluous information; every word earns its place.

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

Completeness4/5

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

For a tool with no parameters and a simple output, the description adequately covers what it returns. However, it lacks details on output structure (e.g., array format) since no output schema is provided. Still, it is sufficient for an AI to understand the tool's role.

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?

There are no parameters, so schema coverage is 100% trivially. The description adds value by listing examples of passenger types (adult, child, senior, student discounts), providing context beyond the empty schema. Baseline for 0 params is 4.

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 the tool retrieves a list of passenger types and discount categories, with specific examples. The verb 'Get' and resource 'list of available passenger types' are precise. It distinguishes from sibling tools that deal with connections, prices, and locations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives. While the purpose is clear, the description lacks information on prerequisites or typical usage context, such as calling this before searching connections.

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

Deploy Server

Other Tools