Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

airline-aircraftType

Generate a random aircraft type for testing, mock datasets, or aviation-related sample data.

Instructions

Returns a random aircraft type.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does disclose the one important trait — output is non-deterministic — but says nothing about the shape of the returned value (an ICAO type code like "B738" versus a free-form name), whether values are drawn from a fixed list, or whether repeated calls can repeat.

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 redundant wording. It is efficient, though the same brevity leaves the return value unexplained.

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?

For a zero-parameter generator the return value is the entire product, yet there is no output schema and the description never says what the value looks like. An agent cannot construct a downstream expectation from this definition without calling the tool and inspecting the result.

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, and the schema correctly declares an empty object with additionalProperties false, so there is nothing parameter-level to explain. Baseline 4 applies.

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 specific verb and resource ("Returns a random aircraft type") plus a key modifier ("random"), so the agent knows this is a value generator rather than a lookup. It does not differentiate itself from near-neighbours such as airline-airplane-name or airline-airplane-iataTypeCode, so the agent cannot tell from the description alone what distinguishes an "aircraft type" from an "airplane 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 when-to-use guidance, no exclusion, and no mention of the sibling lookups that return specific aircraft/airplane values. The agent must infer that this is a sample/filler-data tool from the word "random" alone.

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