Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

finance-accountNumber

Generate a random account number with a customizable length for testing or mock financial data.

Instructions

Generates a random account 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": "finance-accountNumber"
  }
}

Input Schema

NameRequiredDescriptionDefault
lengthNoThe length of the account number.

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?

No annotations are supplied, so the description carries the full behavioral burden. 'Random' hints at non-determinism, but nothing is said about whether output is digits-only, whether it has a fixed default length (the parameter is optional), whether it is suitable for production or only for test data, or what happens with extreme length values. For a generator with no annotation coverage this is a substantial gap.

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 zero filler. The verb and subject appear immediately, so the agent gets the core purpose on the first read.

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 one-parameter generator with no annotations and no output schema, the description should at minimum cover output format (numeric vs. alphanumeric), the default length, and the intended use (test data generation). None of these are present, leaving the agent to guess at the shape of the returned value.

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% for the single 'length' parameter, so the schema already explains it. The description adds nothing about the parameter, and the baseline of 3 applies when the schema does the work. It also leaves the default length for an omitted parameter unstated.

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 account number.' An agent can immediately tell this produces a synthetic account number rather than validating or looking one up. It doesn't explicitly distinguish itself from near siblings like finance-routingNumber or finance-iban, but the resource noun is unambiguous.

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 exclusions, and no mention of alternatives such as finance-iban or finance-routingNumber when a differently-formatted identifier is needed. The agent must infer that this is for test/mock account numbers purely from 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