getRailStatus
Queries live train departures and schedule delays for European transit hubs using transport.opendata.ch.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| station | Yes | Station name (e.g. Zurich HB) |
StatePulse API
TDQS
A3.6/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It only states the tool 'queries live train departures' without disclosing behavioral traits like rate limits, data freshness, permissions, or error handling.
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, well-structured sentence that front-loads the key verb and resource. No extraneous information is present.
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 simple one-parameter query tool with no output schema, the description sufficiently communicates purpose. However, it lacks information about return format or potential limitations.
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?
The schema covers 100% of the single parameter 'station' with a description and example. The tool description adds no further parameter details beyond what the schema provides, resulting in a baseline score.
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 verb 'queries', the resource 'live train departures and schedule delays', the scope 'European transit hubs', and the data source. This distinguishes it from sibling tools like getAirportBoard or getTransitStatus.
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 implies usage for train departures and delays but provides no explicit guidance on when to use this tool versus alternatives. No exclusion criteria or context are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
B3/5.0
Disambiguation2/5
Many tools have overlapping functionality, e.g., auditNetworkHost combines DNS, SSL, and header checks that have dedicated tools (auditDnsSecurity, checkSslExpiry, auditSecurityHeaders). Multiple weather and blockchain tools also overlap in scope, making it difficult for an agent to choose the right tool.
Naming Consistency4/5
Most tools follow a consistent verb_noun pattern (e.g., getAirQuality, checkDnsPropagation), but a few deviate (agentPreflight, capabilitiesDiff) and some use compound names (depositCoordinationBounty). Overall, the pattern is clear but not perfectly uniform.
Tool Count1/5
With 56 tools, the server is far too large for a coherent MCP surface. The number suggests a collection of many unrelated APIs rather than a focused tool set. A typical well-scoped server has 3-15 tools.
Completeness2/5
While the tool set covers many domains, each domain has shallow coverage. For example, blockchain tools miss basic transaction sending and contract deployment; weather tools lack forecasts. The 'requestMissingData' endpoint acknowledges gaps, but the current surface is severely incomplete for a general-purpose API.