Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

airline-airport-iataCode

Generate a random airport and IATA code for testing airline, travel, or booking applications and populating sample data.

Instructions

Generates a random airport.

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-airport-iataCode"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.7/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, and the only behavioral trait it discloses is that output is random. It does not say whether the value is a bare string or a structured object, whether results can repeat across calls, or what format the code takes (e.g., three uppercase letters).

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?

A single sentence with no filler, so it is not bloated. However, the brevity here reflects under-specification rather than economy — one more clause naming the return type would cost little and close the main gap.

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?

The tool is simple (zero parameters, flat schema), which lowers the bar, but there is no output schema and no annotations, so the description is the sole source of truth about the return value — and it never states one. An agent cannot tell whether to expect "LHR" or a JSON object.

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 is 4 and there is nothing the description could add or omit on this dimension.

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 pairs a specific verb ("Generates") with a resource ("airport"), but it is ambiguous about what is actually produced — an airport name, an IATA code, or a full airport object. The tool name says "iataCode" while the description says "airport", and the sibling airline-airport-name suggests a distinct output, so the description does not sharpen the distinction it needs to.

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 statement of when to prefer this over airline-airport-name or any other sibling, and no context about intended use (e.g., seeding mock data, generating test fixtures). The agent must infer the use case entirely from the name.

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