Skip to main content
Glama
mirodn

mcp-server-public-transport

ch_search_stations

Search for Swiss train stations by name or location using public transport data. Find station information to plan travel routes across Switzerland.

Instructions

Search for Swiss train stations by name or location.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
typeNostation

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function that implements the ch_search_stations tool logic. It validates the query, prepares API parameters, fetches data from the Swiss transport API, and handles errors.
    async def ch_search_stations(
        query: str,
        type: Optional[str] = "station"
    ) -> Dict[str, Any]:
        """Search for Swiss stations by name."""
        if not query or not query.strip():
            raise ValueError("Search query cannot be empty")
    
        params = {
            "query": query.strip(),
            "type": type or "station"
        }
    
        try:
            logger.info(f"Searching stations: {query}")
            return await fetch_json(f"{CH_BASE_URL}/locations", params)
        except TransportAPIError as e:
            logger.error(f"CH station search failed: {e}")
            raise
  • tools/ch.py:62-65 (registration)
    The @mcp.tool decorator that registers the ch_search_stations function as an MCP tool with its name and description.
    @mcp.tool(
        name="ch_search_stations",
        description="Search for Swiss train stations by name or location."
    )
  • tools/ch.py:139-144 (registration)
    The register_ch_tools function returns a list of tool functions including ch_search_stations for registration with the MCP server.
    return [
        ch_search_connections,
        ch_search_stations,
        ch_get_departures,
        ch_nearby_stations
    ]
  • server.py:50-50 (registration)
    Top-level registration in the server main function, calling register_ch_tools to add the CH tools (including ch_search_stations) to the MCP instance.
    ch_tools = register_ch_tools(mcp)
Behavior2/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 of behavioral disclosure. It states the tool is for searching, implying a read-only operation, but doesn't cover critical aspects like authentication needs, rate limits, pagination, error handling, or response format. For a search tool with zero annotation coverage, this is a significant gap in transparency.

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, efficient sentence: 'Search for Swiss train stations by name or location.' It is front-loaded with the core purpose and wastes no words, making it highly concise and well-structured for quick understanding.

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?

Given the tool's moderate complexity (2 parameters, 1 required) and the presence of an output schema, the description is minimally adequate. It covers the basic purpose but lacks details on usage context, parameter meanings, and behavioral traits. With no annotations and low schema coverage, it doesn't fully compensate for these gaps, though the output schema may help with return values.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, meaning the input schema provides no descriptions for parameters. The description mentions searching 'by name or location,' which hints at the 'query' parameter's purpose but doesn't explain the 'type' parameter or its default value 'station.' It adds minimal semantic value beyond the schema, failing to compensate for the low coverage.

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 tool's purpose: 'Search for Swiss train stations by name or location.' It specifies the verb ('Search'), resource ('Swiss train stations'), and scope ('by name or location'). However, it doesn't explicitly differentiate from sibling tools like 'ch_nearby_stations' or 'be_search_stations', which prevents a score of 5.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'ch_nearby_stations' for location-based searches or 'be_search_stations' for Belgian stations, nor does it specify prerequisites or exclusions. This leaves the agent with minimal context for tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mirodn/mcp-server-public-transport'

If you have feedback or need assistance with the MCP directory API, please join our Discord server