Skip to main content
Glama

Travel guide

mb_travel_guide
Read-onlyIdempotent

Retrieve route or city travel guides with summaries, FAQs, articles, and matching magazine posts by supplying service, origin, destination, or a search query.

Instructions

MrBilit's guide for a route or city (summary, FAQ, article) and matching travel-magazine posts.

Route guide: service + origin + destination (flight IATA codes, train/bus English slugs such as 'tehran'; hotel: destination city slug only). Magazine: query. Quoted prices can be out of date.

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_travel_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax magazine posts.
queryNoMagazine search, e.g. 'کیش' or 'جاهای دیدنی مشهد'.
originNoFlight: IATA code ('THR'); train, bus, taxi: English city slug ('tehran'); hotel destination: city slug or 'city/hotel' ('mashhad/enghelab').
serviceNoRoute guide for this service; needs destination.
full_textNoReturn long texts uncut instead of clipped.
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. Changed14 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 / properties / query / anyOf
      Removed value: -[
      -  {
      -    "maxLength": 100,
      -    "minLength": 2,
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / query / maxLength
      Added value: +100
    • addedInput schema / properties / query / minLength
      Added value: +2
    • addedInput schema / properties / query / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedInput schema / properties / service / anyOf
      Removed value: -[
      -  {
      -    "enum": [
      -      "flight",
      -      "train",
      -      "bus",
      -      "hotel"
      -    ],
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / service / enum
      Added value: +[
      +  "flight",
      +  "train",
      +  "bus",
      +  "hotel",
      +  null
      +]
    • addedInput schema / properties / service / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedInput schema / title
      Removed value: -"mb_travel_guideArguments"
  2. Changed7 schema fields changedv0.3.0
    • removedInput schema / properties / destination / title
      Removed value: -"Destination"
    • addedInput schema / properties / full_text
      Added value: +{
      +  "default": false,
      +  "description": "Return long texts uncut instead of clipped.",
      +  "type": "boolean"
      +}
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / origin / title
      Removed value: -"Origin"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / properties / service / title
      Removed value: -"Service"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "mb_travel_guideDictOutput",
      -  "type": "object"
      -}New value: +null
  3. First observedv0.1.0

TDQS

A3.7/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 open-world, so the safety profile is covered. The description adds genuinely non-obvious context: content is a summary/FAQ/article rather than structured data, and quoted prices may be stale. It stops short of describing response shape or how clipped vs full text behaves beyond the schema's own note.

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-loaded with the tool's purpose, then the two modes, then the price caveat — a sensible ordering with no filler. The parenthetical listing of IATA codes and English slugs partly restates the schema's origin/destination descriptions, costing a little redundancy.

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?

For a six-parameter, all-optional tool with no output schema, the description explains both operating modes and the content type returned, which is the important part. It leaves undefined the zero-argument default and the mixed query-plus-route case, both of which an agent could plausibly hit given nothing is required.

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%, so the per-parameter formats are already documented. The description adds cross-parameter meaning the schema cannot express: which parameters pair together per service type (route guide needs service + destination; hotel uses destination city slug only; magazine uses query).

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?

The description states a concrete resource: MrBilit guide content (summary, FAQ, article) plus matching magazine posts, and splits it into two named modes (route guide vs magazine). This clearly separates it from booking/search siblings like mb_search_flights or mb_hotel, though no sibling is named explicitly.

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?

It gives mode-selection conditions ('Route guide: service + origin + destination', 'Magazine: query'), which implies when each branch applies. It never says when to prefer this guide tool over lookups such as mb_find_place or mb_city_hotels, and does not state what happens if both modes' parameters are supplied or none are.

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