openbusdata

timetables_api_v1_dataset_by_datasetID

Retrieve a single bus timetable dataset by providing its unique dataset ID. Access schedule details for a specific operator or region.

Instructions

Returns a single dataset

Parameters: datasetID (required): Limit results to a specific data set of a publisher using the data set ID.

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": {
      "kwargs": "<kwargs>"
    },
    "name": "timetables_api_v1_dataset_by_datasetID"
  }
}

Input Schema

Name	Required	Description	Default
`kwargs`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Jul 6, 2026

TDQS

C2.5/5.0

Behavior1/5

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

No annotations provided, and the description fails to disclose any behavioral traits such as idempotency, authentication, or rate limits. The burden falls entirely on the description, which is insufficient.

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 very short with one sentence and a parameter list. It is concise but lacks structure and clarity due to the discrepancy with the schema.

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?

Given the presence of an output schema, return value explanation is not needed. However, the description fails to explain how the parameter (datasetID) relates to the actual schema (kwargs), leaving critical context missing.

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 coverage is 0%, so the description must compensate. It describes a 'datasetID' parameter, but the actual schema contains 'kwargs' instead, leading to a mismatch. This confuses rather than clarifies.

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 'Returns a single dataset' clearly indicates the verb and resource, and the name distinguishes it from the sibling 'timetables_api_v1_dataset' which likely returns all datasets. However, confusion arises from the parameter mismatch with the schema.

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 on when to use this tool versus alternatives like 'timetables_api_v1_dataset'. The description lacks context for selecting the correct tool.

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

Deploy Server