Skip to main content
Glama
sepehr071

mrbilit-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Help center search

mb_help
Read-onlyIdempotent

Search official rules and help-center guides to answer refund, cancellation, ID, baggage, auto-reserve, and change-request questions, returning matching passages.

Instructions

Search MrBilit's official rules, FAQ and help-center guides; returns the best matching passages.

Use for refund and cancellation rules, ID and baggage rules, how auto-reserve works, how to request a change, etc. Passages are plain text with the section they come from. Rules of one fare are in mb_flight_fare_details / mb_search_trains / mb_search_buses instead.

Input Schema

NameRequiredDescriptionDefault
limitNoMax passages.
queryYesQuestion or keywords in Persian, e.g. 'استرداد بلیط قطار' or 'رزرو خودکار'.
sourceNoterms = official rules (refunds, baggage, ID), faq = general FAQ, support = help-center guides and request forms.all
full_textNoReturn long texts uncut instead of clipped.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.0
    • 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 / query / title
      Removed value: -"Query"
    • removedInput schema / properties / source / title
      Removed value: -"Source"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "mb_helpDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.4/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 safety is covered. The description adds genuine behavioral context beyond them: the response is plain-text passages tagged with their source section. It stops short of mentioning result quality, ranking, or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, purpose front-loaded, usage examples second, sibling routing last. No filler and nothing repeated from the schema.

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 usefully explains the return shape (matching passages with source sections) and covers source routing, which is the main ambiguity for this tool. Only minor gaps remain around ranking or result volume, which the limit parameter already bounds.

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%, including the enum semantics for source and the Persian-language expectation for query, so the schema already does the heavy lifting. The description's mention of rules/FAQ/guides loosely mirrors the terms/faq/support enum but adds no new parameter-level detail. Baseline 3 is appropriate.

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 verb and resource ('Search MrBilit's official rules, FAQ and help-center guides') plus the return type ('best matching passages'). It also distinguishes itself from fare-specific siblings by naming mb_flight_fare_details / mb_search_trains / mb_search_buses as the correct route for per-fare rules.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly enumerates the question classes it is for (refunds/cancellation, ID and baggage, auto-reserve, change requests) and gives an explicit exclusion routing fare rules to three named siblings. Both the when and the when-not are covered.

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