Skip to main content
Glama
sepehr071

mrbilit-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Transport companies

mb_companies
Read-onlyIdempotent

Look up airline IATA codes, rail operator IDs, or bus company IDs with Persian and English names to identify codes and filter flight searches.

Instructions

List airlines (IATA code), rail operators or bus companies (id) with Persian and English names.

Use to name a code seen in results (airline 'W5', bus company 4) or to find an airline code for the airlines filter of mb_search_flights. Rail operators repeat under several ids; each row lists all of them. Bus ids 276/278/280 are the taxi classes VIP/Economy/Formal.

Input Schema

NameRequiredDescriptionDefault
modeYesAirlines, rail operators, or bus companies and taxi classes.
limitNoMax companies.
queryNoOptional name or code filter, e.g. 'ماهان', 'IR' or 'Iran Peyma'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.0
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / mode / title
      Removed value: -"Mode"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "mb_companiesDictOutput",
-  "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 cover readOnly, idempotent, openWorld, and non-destructive, so the safety profile is fully declared. The description adds domain-specific behavior beyond the annotations: rail operators repeat under several ids with each row listing all of them, and bus ids 276/278/280 are the taxi classes VIP/Economy/Formal. This is valuable interpretive context.

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 short lines, front-loaded with the resource list, then usage, then the rail/taxi idiosyncrasies. Every sentence earns its place with no filler.

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?

For a 3-param read-only lookup with no output schema, the description covers purpose, usage routing, and result-interpretation quirks. It could mention output ordering or pagination behavior for the limit parameter, but the essentials an agent needs to call and interpret it are present.

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% and the enum for mode is documented. The description adds domain meaning to code fields ('W5' airline, 4 bus company) that helps the agent interpret results, but does not extend the parameter documentation itself. Baseline 3 fits when the schema does the heavy lifting.

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 names the specific resource (airlines, rail operators, bus companies) and the return shape (IATA code, id, Persian/English names). This is a reference-lookup tool clearly distinguished from the sibling search_* tools.

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 states when to use it: to name a code seen in results (airline 'W5', bus company 4) or to find an airline code for the `airlines` filter of mb_search_flights. Names a sibling tool and the routing condition, which is exactly the when-to-use signal an agent needs.

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