Skip to main content
Glama
fastmcp-me

OpenDataMCP

by fastmcp-me
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

rolling-stock

Retrieve rolling stock vehicle data from open datasets. Filter, sort, and select fields to get specific vehicle information.

Instructions

Fetch rolling stock (vehicle) information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of rolling stock entries to return (1-100)
whereNoFilter conditions. Examples: 'fahrzeug_typ = "X"', 'vmax_betrieblich_zugelassen > 100'
offsetNoNumber of rolling stock entries to skip for pagination
selectNoFields to select in the response. Examples: 'fahrzeug_typ,objekt' for basic info, 'vmax_betrieblich_zugelassen,lange_uber_puffer_lup' for technical details
group_byNoGroup rolling stock by specific fields. Example: 'fahrzeug_typ' to group by vehicle type
order_byNoSort rolling stock. Example: 'baudatum_fahrzeug ASC' for oldest first, 'vmax_betrieblich_zugelassen DESC' for fastest first

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Fetch rolling stock information' without revealing that it supports pagination, filtering, grouping, or ordering, nor whether it is a read-only operation. The description adds no behavioral context beyond what the name implies.

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 a single, concise sentence that is front-loaded with the core action. It avoids unnecessary verbosity, though it sacrifices informativeness for brevity. It is not bloated, but could be more helpful with additional context.

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

Completeness2/5

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

For a tool with 6 optional parameters covering filtering, sorting, grouping, and pagination, the description is extremely minimal. It does not explain what kind of data is returned, the meaning of 'rolling stock', or the query syntax beyond what the schema provides. With no output schema, the agent has limited understanding of the response format.

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 input schema provides 100% coverage with descriptive examples for each parameter (limit, where, select, group_by, order_by, offset). The description itself adds no parameter-specific meaning, but since the schema fully documents the parameters, the baseline of 3 is appropriate.

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 states a specific verb ('Fetch') and resource ('rolling stock (vehicle) information'), which is clear and distinct from the sibling tools (rail-traffic-info, railway-lines). However, it does not elaborate on what 'information' encompasses, so it is clear but not fully differentiated beyond the name.

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 guidance is provided on when to use this tool versus the sibling tools. There is no mention of scenarios, exclusions, or alternative selection criteria. An agent would have to infer from the name alone when to choose rolling-stock over rail-traffic-info or railway-lines.

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