Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

location-zipCode

Generates a random localized zip code for a specified state and format, useful for creating realistic test data or mock addresses.

Instructions

Generates a random localized zip 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-zipCode"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoThe state to generate a zip code for.
formatNoThe format the zip code should use.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and largely drops it. It does not say what happens when state is omitted (random state? global zip?), what format values are accepted, whether the state is validated, or whether repeated calls can return duplicates. Only "random" conveys real behavior.

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 with zero filler. It is efficient, though its brevity leans toward under-specification rather than optimal density.

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 simple two-optional-parameter generator with a fully described schema and no output schema, the description is minimally sufficient. It still leaves key call-time questions open, notably default behavior with no parameters and valid format values.

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%, so both parameters are already documented in the schema, making 3 the baseline. The description adds only the notion of "localized," which loosely links state to the output, and says nothing about the format parameter's accepted values.

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?

The description uses a specific verb and resource: "Generates a random localized zip code." An agent can immediately tell this is a data-generation utility distinct from lookup-style siblings such as location-city or location-state. It stops short of 5 because it never contrasts itself with those siblings explicitly.

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 when-to-use guidance, no statement about when a generator is preferable to a real lookup, and no mention of alternatives. The phrase "localized" weakly implies the state parameter scopes the result, but the agent must infer that.

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