Skip to main content
Glama

Site notices

mb_notices
Read-onlyIdempotent

Retrieve current service or route notices for flights, trains, buses, taxis, and hotels to check 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 notices match (/flights/THR-MHD, /trains/tehran-mashhad, /hotel/mashhad). site_wide_active counts every active notice. Use before recommending a trip.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mb_notices"
  }
}

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. Changed7 schema fields changedv0.5.0
    • removedInput schema / properties / destination / anyOf
      Removed value: -[
      -  {
      -    "pattern": "^[\\w()-]{2,40}(/[\\w()-]{2,60})?$",
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / destination / pattern
      Added value: +"^[\\w()-]{2,40}(/[\\w()-]{2,60})?$"
    • addedInput schema / properties / destination / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedInput schema / properties / origin / anyOf
      Removed value: -[
      -  {
      -    "pattern": "^[\\w()-]{2,40}(/[\\w()-]{2,60})?$",
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / origin / pattern
      Added value: +"^[\\w()-]{2,40}(/[\\w()-]{2,60})?$"
    • addedInput schema / properties / origin / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedInput schema / title
      Removed value: -"mb_noticesArguments"
  2. 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
  3. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent, read-only, open-world call, so the bar is lower. The description still adds useful context by explaining that route codes construct the site path (/flights/THR-MHD, /trains/tehran-mashhad) that notices are matched against, which tells the agent how matching actually works rather than just what the inputs are.

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?

Four compact sentences, front-loaded with what the tool returns and backed by concrete path examples. The reference to 'site_wide_active' is dropped in without explaining whether it is a field, a flag, or an option, which is the one loose thread.

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

Completeness3/5

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

The tool is a simple read with a well-documented schema, so it is nearly complete. However, with no output schema, the description never says what a notice record contains, and the unexplained 'site_wide_active' term leaves the agent guessing about the response shape.

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%, with per-parameter examples and an enum for service, so the schema carries the parameter load. The description's route-path examples corroborate the schema but add no new syntax, defaults, or edge-case behavior (e.g., what happens when only one of origin/destination is supplied).

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?

States a specific verb and resource: notices MrBilit shows on its pages, with concrete categories (disruptions, rule changes, payment options) and the scoping dimension (service or route). No sibling tool overlaps this capability, so differentiation is implicit rather than stated, which keeps it just below a 5.

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?

Ends with an explicit usage cue, 'Use before recommending a trip,' which tells the agent where this fits in a workflow. It gives no when-not condition and names no alternative tool, so it stops short of full routing guidance.

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