Skip to main content
Glama

Transport companies

mb_companies
Read-onlyIdempotent

Lists airlines, rail operators, and bus companies with Persian and English names and IATA or ID codes, so you can match codes in results or find values for the airlines filter.

Instructions

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

Use to name a code seen in results or to find a code for the airlines filter. Bus ids 276/278/280 are the taxi classes VIP/Economy/Formal.

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": {
      "mode": "<mode>"
    },
    "name": "mb_companies"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.5.0
    • changedInput schema / properties / mode / description
      Previous value: -"Airlines, rail operators, or bus companies and taxi classes."New value: +"Airlines, rail operators, or bus companies."
    • removedInput schema / properties / query / anyOf
      Removed value: -[
      -  {
      -    "maxLength": 60,
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / query / maxLength
      Added value: +60
    • addedInput schema / properties / query / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedInput schema / title
      Removed value: -"mb_companiesArguments"
  2. 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
  3. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already establish this as a safe, idempotent, read-only, open-world lookup, so the description adds genuinely non-obvious behavior: airlines are keyed by IATA code but rail/bus by numeric id, and bus ids 276/278/280 are the taxi classes VIP/Economy/Formal. It does not mention result ordering, pagination beyond the limit, or empty-result behavior, 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.

Conciseness4/5

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

Three short, front-loaded sentences with no filler: purpose, use case, then a quirk note. The telegraphic parenthetical '(id)' and the crowded last sentence slightly reduce scannability, but every sentence carries information.

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 three-parameter, read-only lookup with full schema coverage and no output schema, the description supplies purpose, usage, identifier semantics and a data quirk. What is missing (result shape, ordering, behavior of `query` against Persian vs Latin names) is modest rather than blocking.

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% and the enum is documented, so the baseline is 3; the description earns above that by explaining what the identifiers mean per mode and by enumerating the special taxi-class ids, which the schema does not convey. It says nothing extra about `limit` or `query` matching semantics (name vs code, Persian vs English).

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 first sentence gives a specific verb (List) and resource (airlines, rail operators, bus companies) and even disambiguates the identifier type per mode (IATA code vs id). This is enough to separate it from siblings like mb_search_flights or mb_search_buses, which search inventory rather than list operator directories.

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 names two concrete use cases: resolving a code already seen in results, and looking up a code to feed the `airlines` filter. That is clear contextual guidance with no exclusions or anti-patterns (e.g. 'do not use to price tickets'), so it falls short of a full when/when-not statement.

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