Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

location-buildingNumber

Generates a random building number for address data. Use it to populate realistic street-address fields when creating sample or test records.

Instructions

Generates a random building 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-buildingNumber"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the single most important trait — output is randomly generated, not a real lookup — but says nothing about the value's format (numeric only? alphanumeric suffix?), locale, or whether it is guaranteed unique or reproducible, all of which matter for a data-generation tool.

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 short sentence with no filler, and the operative fact (random generation of a building number) is stated immediately. Its brevity borders on under-specification rather than padding, so it is not penalized heavily here.

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 zero-parameter generator the description covers the essentials, but with no output schema present the agent has no way to learn the shape of the returned building number (e.g., "221B" vs "221"). One clause on output format would make this complete.

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 (empty object schema, additionalProperties=false), so there is no parameter meaning for the description to add; baseline for a parameterless tool 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?

The description pairs a specific verb ("Generates") with a specific resource ("a random building number"), so the agent immediately knows the tool's output type. It does not distinguish this from sibling generators such as location-street or location-secondaryAddress, which would have made it a 5.

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 guidance on when to use this versus the many sibling location generators, and no stated prerequisites or exclusions. The agent must infer that this is a test-data/fixture generator from the word "random" alone.

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