Skip to main content
Glama
sepehr071

mrbilit-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Travel guide

mb_travel_guide
Read-onlyIdempotent

Get route or city travel guides with summaries, FAQs, articles, and matching magazine posts for flights, trains, buses, or hotels; verify live prices with search tools.

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. Editorial text: prices or rules quoted in it can be out of date; use the search tools for live prices.

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. 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
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that — editorial text may quote out-of-date prices or rules, and live data must come from search tools — which is exactly the kind of caveat annotations cannot express.

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?

The purpose leads, followed by compact mode-specific clauses; every sentence carries information and nothing is repeated. The telegraphic 'service + origin + destination' fragments are efficient but slightly terse, keeping it just below a 5.

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?

With no output schema, the description does address what comes back (summary, FAQ, article, magazine posts) and flags content-staleness, so an agent can call it correctly. It could say more about how many results or clipped-vs-full-text behavior, but the essentials are present.

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 baseline is 3. The description goes slightly beyond the per-parameter schema by tying parameters together — which combination (service+origin+destination vs. query) activates each mode and the special rule that hotel only needs the destination city slug — which is cross-parameter semantics the schema fields do not state.

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 names a concrete resource — MrBilit's guide content (summary, FAQ, article) plus travel-magazine posts — so an agent knows this returns editorial content rather than prices or availability. It implicitly separates itself from the search/booking siblings via the 'use the search tools for live prices' line, but it does not differentiate from other content-ish siblings such as mb_find_place, mb_notices, or mb_help.

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?

It gives clear selection rules: route-guide mode requires service + origin + destination, while magazine mode takes a query, and it redirects agents to search tools for live prices. There is no explicit 'do not use this for X' or contrast against the other non-search siblings, so it falls 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