Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

location-state

Returns a random state or equivalent first-level administrative entity for a locale's country; optionally returns abbreviated names. Use it to populate sample location data or test locale-specific forms.

Instructions

Returns a random state, or other equivalent first-level administrative entity for the locale's country such as a province, region, or prefecture.

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

Input Schema

NameRequiredDescriptionDefault
abbreviatedNoIf true this will return abbreviated state names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations at all, the description carries the full disclosure burden. It does convey two useful traits — the output is randomized and it is locale-scoped — but says nothing about the return type (plain string vs. structured object), whether repetition is possible, or whether any locale must be configured first, which matters for a generator with no annotations and no output schema.

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?

One front-loaded sentence with the core behavior first and the locale clarification second; no filler. The qualifier 'or other equivalent first-level administrative entity' is slightly wordy but earns its place by broadening the resource definition.

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 one-optional-parameter generator with no output schema, the description covers what is returned and that it is random. It still leaves the agent guessing about the concrete return shape and the locale precondition, which are the only remaining things needed to call and interpret it correctly.

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 optional parameter 'abbreviated' is fully documented in the schema itself. The description adds nothing about it (e.g. what an abbreviation looks like, or that it only affects certain locales), so the baseline 3 for schema-covered parameters 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 state') and immediately broadens it to the locale-equivalent first-level administrative entity (province, region, prefecture), which implicitly separates it from siblings like location-city or location-county. It never names a sibling directly, so differentiation is inferred from the scope wording rather than stated.

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 phrase 'for the locale's country' hints that output depends on an active locale setting, which is the main usage-relevant precondition, but it is never spelled out as a requirement. There is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as location-city when a lower-level entity is wanted.

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