Skip to main content
Glama
sepehr071

mrbilit-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Bus seat map

mb_bus_seats
Read-onlyIdempotent

Get a bus seat map showing free, female-sold, male-sold, and unavailable seats in a row-by-row layout, plus seating rules, using a bus ID.

Instructions

Seat map of one bus: free seat numbers, seats sold to women and to men, and a row-by-row layout.

layout: one line per row from the front; each seat is its number plus a mark: none = free, w = sold to a woman, m = sold to a man, x = not sold online; '|' = the aisle (seats on the same side of it are neighbours), '--' = no seat, 'DR' = driver. Rule text (who may sit where) is in seat_rules. price_toman is null for most buses: use the search price. bus_id expires: take it from a fresh search.

Input Schema

NameRequiredDescriptionDefault
bus_idYesbus_id from a fresh mb_search_buses result, e.g. 55983988.

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, and the description adds substantial context beyond that: the full layout legend (w/m/x/|/--/DR), the note that rule text lives in seat_rules, that price_toman is null for most buses, and that bus_id expires. This is unusually rich behavioral disclosure.

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?

Purpose is front-loaded in the first sentence, and the layout legend, though lengthy, earns its place because there is no output schema to explain the marks. Slightly dense but no wasted sentences.

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, the description carries the full burden of explaining the return format, and it does so thoroughly via the row-by-row legend and the price/rule pointers. An agent has everything needed to call and interpret the result.

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% with a single parameter, so the schema already documents bus_id. The description adds genuine meaning beyond the schema by warning that bus_id expires and must come from a fresh search, which changes how the agent should source the value.

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?

States a specific verb+resource ('Seat map of one bus') and immediately enumerates the returned content: free seats, gender-sold seats, and row layout. It is clearly distinguishable from list/search siblings like mb_search_buses, which the description implicitly references for obtaining a fresh bus_id.

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?

Usage is implied rather than stated: it tells the agent to take bus_id from a fresh search and to use the search price when price_toman is null, which is useful operational guidance. However, there is no explicit when-to-use vs. when-not statement or named alternative, so it sits at the minimum-viable level.

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