Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

airline-flightNumber

Generate random flight numbers for fake data, testing, or mock records. Customize digit length and pad numbers with leading zeros to fit your data format.

Instructions

Returns a random flight number.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "airline-flightNumber"
  }
}

Input Schema

NameRequiredDescriptionDefault
lengthNoThe number or range of digits to generate.
addLeadingZerosNoWhether to pad the flight number up to 4 digits with leading zeros.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the key non-determinism trait ("random"), but says nothing about output type/format, whether results are guaranteed unique, default behavior when no parameters are passed, or that the value is fabricated rather than retrieved. For a generator with zero annotation coverage, that is a substantial gap.

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?

A single front-loaded sentence with zero filler. However, its brevity borders on under-specification for a tool with two behaviorally meaningful optional parameters; one clause on default output would have been worth the words.

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?

The tool is simple: zero required parameters, two optional fully-documented parameters, no output schema, no nested objects. Combined with the schema, the sentence is close to sufficient. It falls short only on stating the default call behavior and the fact that output is fabricated data.

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%: both `length` (number or {min,max} range) and `addLeadingZeros` (pad to 4 digits) are fully documented in the schema. The description adds no additional meaning about how length interacts with padding or what the defaults are. Baseline 3 applies when the schema does all the work.

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?

States a concrete verb and resource: "Returns a random flight number." An agent immediately knows this is a synthetic flight-number generator, which is distinct from the other faker-style sibling generators (seat, recordLocator, airport-iataCode). It does not explicitly name a sibling or scope constraint, but the resource is unambiguous.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no mention that this produces fake/test data rather than looking up a real flight, and no reference to any alternative. The agent must infer the intended test-data context entirely from the tool name and the faker-style sibling family.

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