mrbilit-mcp

Overview Schema Source Related Servers Discussions Admin

Help center search

mb_help

Read-onlyIdempotent

Search MrBilit's official rules, FAQ, and help-center guides to find matching passages for refund, cancellation, ID, and baggage questions.

Instructions

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

Use for refund, cancellation, ID and baggage rules. Rules of one fare are in mb_flight_fare_details / mb_search_trains / mb_search_buses instead.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "mb_help"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Max passages.
`query`	Yes	Question or keywords in Persian, e.g. 'استرداد بلیط قطار' or 'رزرو خودکار'.
`source`	No	terms = official rules, faq = general FAQ, support = help-center guides.	all
`full_text`	No	Return long texts uncut instead of clipped.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.5.0Nov 7, 2026

changedInput schema / properties / source / description

Previous value: -"terms = official rules (refunds, baggage, ID), faq = general FAQ, support = help-center guides and request forms."New value: +"terms = official rules, faq = general FAQ, support = help-center guides."

removedInput schema / title
```
Removed value: -"mb_helpArguments"
```

Changed5 schema fields changedv0.3.0Oct 17, 2026

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

First observedv0.1.0Oct 5, 2026

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 the safety profile carries little weight here. The description still adds value by stating that results are ranked matching passages rather than documents, and by scoping out single-fare rules. It does not say whether results include source citations or how to page past the limit, which keeps it below a 5.

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?

Two sentences, the positive scope front-loaded before the redirect. Every clause carries information an agent needs; nothing is redundant with the title or 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's mention of returning best matching passages does useful work, and the exclusion of per-fare rules prevents a common mis-route. What is missing is modest but real: no note on citation/linking of passages or on how limit interacts with multi-passage answers.

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%: query (with a Persian example), source enum meanings, limit bounds and full_text clipping behavior are all documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 gives a specific verb and resource ('Search MrBilit's official rules, FAQ and help-center guides') plus the return shape ('best matching passages'). It also draws a clear boundary against the fare-detail and search-tool siblings, so an agent can pick it without opening any schema.

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?

It explicitly names the topics this tool covers (refund, cancellation, ID, baggage) and redirects one specific case (rules of a single fare) to three named alternatives. That is when-to-use, when-not-to-use, and named alternatives in two sentences.

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