Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

airline-airplane-iataTypeCode

Generates a random airplane IATA type code for testing, mock data, and airline data modeling.

Instructions

Generates a random airplane model.

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-airplane-iataTypeCode"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does disclose the key trait that output is random (nondeterministic), but it does not say what form the result takes, whether it is a string, whether it maps to an IATA type code, or whether repeated calls yield distinct values.

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 short sentence with zero filler. The action and the resource are front-loaded, so the definition is appropriately sized for a zero-parameter generator.

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?

There is no output schema and no annotations, so the description must explain the return value, but it does not. 'Airplane model' could mean a manufacturer and model name, an IATA aircraft type code (as the tool name suggests), or a free-text label, and an agent cannot know what it will receive.

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?

The tool takes zero parameters, so the baseline for this dimension is 4. The description adds nothing that is needed, because there is nothing to disambiguate, and the empty schema is self-explanatory.

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 description states a specific verb and resource: "Generates a random airplane model." However, it does not distinguish this tool from clearly related siblings such as airline-airplane-name or airline-aircraftType, which plausibly also return randomness-derived aircraft data, so an agent cannot tell which generator to pick.

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 versus the siblings, no mention of alternatives, and no statement of exclusions. The only usable signal is the implied 'use when you need a random value,' which is inferred rather than stated.

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