Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

location-county

Generate a random county or equivalent second-level administrative region for a locale's country to populate test data and localized sample locations.

Instructions

Returns a random localized county, or other equivalent second-level administrative entity for the locale's country such as a district or department.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

A3.5/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 does disclose the most important trait, that output is randomly generated, and that output varies by the surrounding locale's country. It does not say whether the locale is taken from ambient configuration or is fixed, nor what the returned value looks like (bare name vs. object with codes).

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 that names the primary case before the country-specific fallbacks. Slightly extended by the district/department examples, but that clause does real work clarifying the generalized scope.

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?

Low-complexity tool with no parameters, no annotations, and no output schema, so the description is nearly sufficient. The remaining gap is the return shape and the source of the locale that drives the result, which an agent would need to interpret the output correctly.

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 schema imposes nothing an agent could misread. The description adds the useful note that the entity class varies by country, which is the only semantic an agent could need here.

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 localized county") and generalizes correctly to equivalent second-level entities like districts or departments. That framing implicitly separates it from location-state (first-level) and location-city, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The word "random" plus "localized" implies the faker-style test-data use case, but there is no explicit statement of when to use this versus location-city or location-state, and no exclusion of cases where a real (non-random) lookup is needed. Usage 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