Skip to main content
Glama
sepehr071

mrbilit-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Train stops

mb_train_stops
Read-onlyIdempotent

Fetch every station a train stops at, in order, with dates and local times. Pass a class_id from train search results; sold-out classes work, but train numbers do not.

Instructions

Every station a train stops at, in order, with the date and local time at each.

Pass a class_id from mb_search_trains (sold-out classes work too; never a train number). The first stop can be before your station (a Tehran-Mashhad train may start in Qom).

Input Schema

NameRequiredDescriptionDefault
class_idYesclass_id of a train class from a fresh mb_search_trains result, e.g. 9847134.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.0
    • removedInput schema / properties / class_id / title
      Removed value: -"Class Id"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "mb_train_stopsDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the bar is lower, and the description still adds genuinely non-obvious behavior: the first stop may precede the user's boarding station (Tehran-Mashhad train starting in Qom), and sold-out classes remain queryable. Return format is conveyed in one clause.

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?

Three short sentences, zero filler, and the payload description is front-loaded before the parameter sourcing and the Qom caveat. Every sentence carries distinct information.

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

Completeness5/5

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

With no output schema and a single 100%-covered parameter, the description supplies exactly the missing pieces: what comes back, where the argument comes from, and a counterintuitive ordering caveat.

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?

Schema coverage is 100% and the schema already defines class_id, so baseline would be 3; the description goes beyond it by constraining the value's provenance (from a fresh mb_search_trains result) and warning against passing a train number instead.

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 names a specific verb+resource ('every station a train stops at, in order') and even characterizes the return payload (date and local time per stop), which cleanly separates it from mb_search_trains and the other train siblings.

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

Usage Guidelines4/5

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

It states the prerequisite explicitly (pass a class_id from mb_search_trains) plus two exclusions: sold-out classes are usable and a train number never is. It stops short of naming an alternative tool for any other case, so it is clear context rather than a full when/when-not map.

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