Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

location-secondaryAddress

Generate a random localized secondary address, such as an apartment or room number, to complete a given address with realistic location details.

Instructions

Generates a random localized secondary address. This refers to a specific location at a given address such as an apartment or room number.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It usefully discloses two traits an agent could not assume: output is random and locale-dependent. However, it does not say how the locale is determined (host environment, configuration, session) or what shape the returned string takes, which matters for a generator with 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the generative action and followed by a definition of the otherwise ambiguous term "secondary address." Nothing is redundant and nothing needed is buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter generator with no annotations, this covers the essentials: what it produces, that output is random, and that it is localized. The remaining gap is how localization is resolved, which the brief description leaves open but which is minor for a fake-data tool.

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 there is no parameter semantics to explain and the baseline of 4 applies. The description correctly implies no inputs are required.

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 pairs a specific verb ("Generates") with a specific resource ("random localized secondary address") and then defines the term with concrete examples (apartment or room number), which implicitly separates it from siblings like location-streetAddress. It is clear, though it never explicitly contrasts with a named sibling.

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?

Usage is only implied: an agent can infer this is for populating a secondary-address field with fake data. There is no statement of when to prefer it over location-streetAddress or when it should not be used, and no prerequisites are mentioned.

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