Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

phone-number

Generate random phone numbers in human, national, or international styles for testing, demos, and placeholder data.

Instructions

Generates a random phone 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": "phone-number"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleNoStyle of the generated phone number: 'human' (default), 'national', or 'international'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the key behavioral trait that the output is randomly generated (i.e., synthetic data, not a real number), which is genuinely useful. However, it says nothing about the return value's format — a bare string versus a formatted human-readable value — or whether output depends on locale, which matters for a generator whose only knob is a style enum.

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 or redundancy. It is front-loaded with the verb and resource, though it is so terse that it leaves no room for the guidance a caller would benefit from.

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?

This is a low-complexity, zero-required-parameter tool, so the bar is modest. Still, with no output schema and no annotations, the description should state what comes back (a string, and in what format), which it does not. Otherwise it is adequate for the tool's simplicity.

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%: the single optional 'style' parameter is fully documented in the schema with its three enum values and the 'human' default. The description adds no information about the parameter beyond what the schema provides, so the baseline of 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?

The description states a specific verb and resource: "Generates a random phone number." That is enough for an agent to distinguish it from sibling resources like phone-imei or finance-creditCardNumber, which target different data types. The only gap is that it does not explicitly disclaim overlap with the phone-imei sibling, though the resource noun already separates them.

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?

The description gives no when-to-use guidance, no exclusions, and names no alternatives. An agent must infer from the tool name alone that this is for fabricating sample phone numbers rather than validating or looking up real ones.

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