Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

airline-seat

Generates a random airline seat number and letter for a specified aircraft type (narrowbody, regional, or widebody). Use it to create realistic seat assignments for test data and mock bookings.

Instructions

Generates a random seat.

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-seat"
  }
}

Input Schema

NameRequiredDescriptionDefault
aircraftTypeNoThe aircraft type. Can be one of 'narrowbody', 'regional', 'widebody'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.5/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 burden of behavioral disclosure, yet it says nothing about the output format, whether values are deterministic or seeded, or whether aircraftType changes the result. The only behavior conveyed is the word 'random', which is already implied by the tool name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is a single front-loaded sentence with no wasted words, which is structurally sound. However, its brevity stems from under-specification rather than efficiency, so it does not fully earn its place.

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

Completeness2/5

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

This is a simple tool with zero required parameters and no output schema, so the description is the only place to document the return format such as a seat string example and the effect of aircraftType. Neither is provided, leaving a real gap for an agent that must consume the result.

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 single optional aircraftType parameter is fully documented with an enum in the schema, so the baseline of 3 applies. The description adds no meaning beyond the schema, not even clarifying that aircraftType may influence the generated seat.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The sentence 'Generates a random seat' names a verb (generates) and resource (seat), but it essentially restates the tool name 'airline-seat' plus the word 'random'. It gives no sense of what the generated value looks like (e.g., '12A') or how it differs from the many sibling faker-style generators, so the purpose is only minimally clarified beyond the name.

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 guidance on when to use this tool, when not to, or how it relates to siblings like airline-aircraftType or airline-recordLocator. An agent can infer only that this produces fake seat data; nothing tells it whether this is the right generator for a given task.

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