Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

finance-pin

Generates a random PIN with a configurable length for testing, mock data, or placeholder authentication codes.

Instructions

Generates a random PIN.

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": "finance-pin"
  }
}

Input Schema

NameRequiredDescriptionDefault
lengthNoThe length of the PIN to generate.

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?

With no annotations, the description carries the full behavioral burden, yet it says nothing about whether the PIN is purely numeric, the default length when 'length' is omitted, or whether the randomness is cryptographically secure — a material concern for anything used as a credential. These omissions are significant for a security-sensitive generator.

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 five-word sentence with no filler and the core action front-loaded. It is as short as it can be, though that brevity comes at the cost of detail scored elsewhere.

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

Completeness2/5

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

For a simple one-parameter tool the gap is still noticeable: no default length, no return type or format stated, and no output schema to fall back on. An agent cannot predict what the returned PIN looks like (string vs. number, leading zeros) from this definition.

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 the single 'length' parameter is already documented in the schema, and the description adds no defaults, ranges, or format constraints beyond that. The baseline of 3 applies when the schema does the heavy lifting.

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 names a specific verb and resource ("Generates a random PIN"), which is unambiguous about the operation. It does not distinguish this from similar generator siblings such as finance-creditCardCVV or finance-accountNumber, but the resource is distinct enough that an agent can identify it.

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 not to use it, and no reference to an alternative tool for generating other credential-like values. The purpose implies usage, but nothing in the text actively routes the agent.

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