Skip to main content
Glama

Bus seat map

mb_bus_seats
Read-onlyIdempotent

Retrieve a bus seat map showing free seats, seats sold to women or men, and the row-by-row layout so you can identify available seats before booking.

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; seat = number + mark (none free, w woman, m man, x not sold online); '|' aisle, '--' no seat, 'DR' driver. price_toman is null for most buses: use the search price.

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": {
      "bus_id": "<bus_id>"
    },
    "name": "mb_bus_seats"
  }
}

Input Schema

NameRequiredDescriptionDefault
bus_idYesbus_id from a fresh mb_search_buses result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.0
    • changedInput schema / properties / bus_id / description
      Previous value: -"bus_id from a fresh mb_search_buses result, e.g. 55983988."New value: +"bus_id from a fresh mb_search_buses result."
    • removedInput schema / title
      Removed value: -"mb_bus_seatsArguments"
  2. 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
  3. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so safety is covered. The description adds behavior an agent cannot infer from structured fields: the gender-based sale encoding (w/m/x marks), driver and aisle notation, and the caveat that price_toman is null for most buses and the search price should be used instead.

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?

Front-loads the one-sentence purpose, then supplies a compact legend for the layout string, which is genuinely needed because there is no output schema. The legend is dense but every token earns its place; only slight redundancy exists between the opening sentence and the mark definitions.

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 required parameter, the description must carry the return-value burden, and it does: it names all returned components, decodes the layout characters, and flags the null-price edge case with a workaround. An agent could parse and present the result correctly from this text alone.

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?

Schema description coverage is 100% and the single bus_id parameter already documents its source ('bus_id from a fresh mb_search_buses result'), which the description merely echoes. The description adds no additional parameter-level semantics such as format or validity constraints beyond the schema's minimum of 1.

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 resource with scope ('Seat map of one bus') and enumerates exactly what the caller gets back: free seat numbers, seats sold to women and to men, and a row-by-row layout. This is clearly distinguishable from the sibling mb_search_buses, which locates buses rather than detailing one bus's seating.

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?

Gives a clear prerequisite: the bus_id must come from a fresh mb_search_buses result, which both names the alternative tool and implies this is a follow-up drill-down step. It does not state explicit exclusions (e.g. don't use for price lookup), so it falls short of a full when/when-not treatment.

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