Skip to main content
Glama
sepehr071

mrbilit-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Site notices

mb_notices
Read-onlyIdempotent

Retrieve active MrBilit notices by service or route to see disruptions, rule changes, and payment options before recommending a trip.

Instructions

Notices MrBilit currently shows on its pages (disruptions, rule changes, payment options), for a service or route.

Route codes build the site path the notice rules match against: /flights/THR-MHD, /trains/tehran-mashhad, /hotel/mashhad. search_mode limits a flight notice to domestic or international searches; site_wide_active counts every active notice, not only these. Use before recommending a trip, alongside the search tools.

Input Schema

NameRequiredDescriptionDefault
originNoFlight: IATA code ('THR'); train, bus, taxi: English city slug ('tehran'); hotel destination: city slug or 'city/hotel' ('mashhad/enghelab').
serviceNoWhich pages; any = every active notice.any
destinationNoFlight: IATA code ('THR'); train, bus, taxi: English city slug ('tehran'); hotel destination: city slug or 'city/hotel' ('mashhad/enghelab').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.0
    • removedInput schema / properties / destination / title
      Removed value: -"Destination"
    • removedInput schema / properties / origin / title
      Removed value: -"Origin"
    • removedInput schema / properties / service / title
      Removed value: -"Service"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "mb_noticesDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.1/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. The description still adds real value by explaining how route codes map to site paths, but it also references `search_mode` and `site_wide_active`, which do not exist in the schema — useful-sounding context that an agent cannot act on.

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 purpose in one clean sentence, then a second block on route codes and behavior. Slightly dense but every sentence is doing work; no filler.

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

Completeness4/5

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

For a read-only, zero-required-parameter lookup with full schema coverage and no output schema, the definition covers when and how to call it. It omits any hint of the notice payload shape and references params the schema lacks, which are minor gaps.

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 coverage is 100%, so origin/destination format rules and the service enum are already documented, making 3 the baseline. The path-construction explanation adds some framing, but the mention of undeclared parameters (search_mode, site_wide_active) creates confusion rather than clarity.

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 resource (site notices for disruptions, rule changes, payment options) and its scope (per service or route). It is immediately distinguishable from every sibling, which are all search/price/lookup tools rather than notice retrieval.

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?

"Use before recommending a trip, alongside the search tools" gives a clear usage context and positions it relative to siblings. It does not state exclusions or when not to call it, so it stops short of a 5.

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