Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

location-countryCode

Generate a random ISO 3166-1 country code in alpha-2, alpha-3, or numeric format for testing, seeding, or placeholder data.

Instructions

Returns a random ISO_3166-1 country code.

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": "location-countryCode"
  }
}

Input Schema

NameRequiredDescriptionDefault
variantNoThe code to return. Can be either 'alpha-2', 'alpha-3', or 'numeric'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.3/5.0
Behavior3/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 non-obvious trait — the value is 'random' and thus non-deterministic — which is genuinely useful, but it omits what happens when the optional variant is omitted (presumably alpha-2) and says nothing about output format beyond the concept of a code.

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 resource and the defining random behavior front-loaded. There is no filler.

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?

For a trivial generator with no output schema, the description covers what is returned but not the default variant when the optional parameter is omitted — the one detail an agent needs to call it correctly at zero required parameters.

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 parameter is an enum with documented values, so the schema already does the work. The description says nothing about variant or the default behavior when it is not supplied, so it adds no meaning beyond the schema.

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 concrete verb and resource: 'Returns a random ISO_3166-1 country code.' This distinguishes it adequately from the sibling location-country (a name, not a code), but it never explicitly says so, leaving the distinction implicit.

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?

No guidance on when to use this versus location-country or other location siblings, and no note about the common case for generating sample data. The agent must infer the use case from the name 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