Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

location-streetAddress

Generate a random localized street address; enable useFullAddress to return a complete address instead of only the street.

Instructions

Generates a random localized street address.

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

Input Schema

NameRequiredDescriptionDefault
useFullAddressNoWhen true this will generate a full address. Otherwise it will just generate a street address.

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 two genuine behaviors beyond the schema — output is randomized and locale-dependent — but it never explains what determines the locale (there is no locale parameter) or whether the address is synthetic/real-world plausible.

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 front-loaded sentence with no filler; the key qualifiers ('random', 'localized') appear immediately.

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 one-parameter, non-destructive generator with a fully documented schema and no output schema, the description is minimally adequate. The notable gap is the unstated source of localization, which an agent cannot infer from any structured field.

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 useFullAddress is fully documented in the schema, including the true/false semantics. The description adds nothing about it, so baseline 3 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: 'Generates a random localized street address.' An agent knows exactly what it produces, though nothing distinguishes it from siblings such as location-street or location-secondaryAddress, which sound closely related.

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 mention of when to prefer location-street or location-secondaryAddress, and no prerequisites. Usage is only implied by the tool name and the word 'random'.

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