Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

airline-recordLocator

Generates a random airline booking reference number, with options to allow numeric characters and visually similar characters.

Instructions

Generates a random record locator (booking reference 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-recordLocator"
  }
}

Input Schema

NameRequiredDescriptionDefault
allowNumericsNoWhether to allow numeric characters.
allowVisuallySimilarCharactersNoWhether to allow visually similar characters such as '1' and 'I'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose the key behavioral trait — that the output is random, not looked up. It says nothing about the returned value's shape or length, whether collisions are possible, or whether repeated calls are independent, which matters for a generator.

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?

A single front-loaded sentence with a parenthetical clarification; every clause earns its place and nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a trivial two-optional-boolean generator this is nearly adequate, and no output schema exists to explain the return. The main gap is that an agent cannot tell whether it receives a string, its typical length, or a wrapper object — details the description should supply given no output schema.

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%, with both booleans (allowNumerics, allowVisuallySimilarCharacters) documented in the schema itself, so the baseline is 3. The description adds no meaning beyond the schema — it never mentions that the generated value's character set is configurable.

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 — "Generates a random record locator" — and glosses the term as "booking reference number" so an agent needs no domain knowledge. No sibling in the list produces booking references, so it is unambiguous by name and by description.

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

Usage Guidelines3/5

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

Usage is only implied: it is a data-generation/fixture tool, and nothing states when to reach for it or that it should not be used to mint real bookings. No alternatives are named, though none of the sibling tools overlap in output.

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