Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

airline-airplane-name

Generates a random airplane model name for testing, mock data, or airline-related sample content.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.4/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 correctly discloses the key behavioral trait, that output is non-deterministic, which is the main thing an agent needs to know before calling. It does not disclose the returned format (e.g., manufacturer plus model designator), value distribution, or whether repeated calls may return duplicates.

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 the essential information front-loaded and no filler. Nothing in the description could be removed without losing meaning.

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?

With no parameters, no annotations, and no output schema, the description is the only source of information about the return value, and it never shows what an airplane model string looks like. For a trivial generator this is a modest but real gap that an example value would close.

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, which establishes the baseline of 4 per the rubric. The description adds nothing on parameters because there is nothing to add, 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.

Purpose4/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 airplane model." An agent immediately knows this is a synthetic-value generator returning an aircraft model string, which distinguishes it from neighbors like airline-airline-name or airline-airport-name. It stops short of naming any sibling or noting the slight mismatch between the tool name (airplane-name) and the described output (airplane model).

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?

The word "random" implies test-data or placeholder generation, but there is no explicit when-to-use, when-not-to-use, or pointer to alternative generators for related needs. The agent must infer the use case from the tool's faker-style 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