Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

finance-routingNumber

Generate a random routing number for testing banking forms, sample data, or mock financial records.

Instructions

Generates a random routing 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-routingNumber"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations present, the description carries the full disclosure burden, and it does convey the single most important behavioral trait: the value is randomly generated, not looked up or deterministic. However, it omits the output format (digit count, separators), whether the result is checksum-valid per ABA rules, and whether repeated calls may collide — all relevant for a generator.

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 no filler, hedging, or redundant restatement of the name. For a zero-argument generator this is an appropriate size, with the core fact ('random routing number') stated immediately.

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?

With no annotations and no output schema, the description is the only source of information about the return value, and it never says what a generated routing number looks like or whether it is structurally valid. For a tool this simple that is a modest but real gap; one clause on output format would make it 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, so the baseline is 4 and there is no parameter meaning the description needs to compensate for. Nothing in the schema requires clarification that the description leaves unaddressed.

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 ('routing number') and adds the qualifier 'random', so an agent can tell it produces synthetic ABA routing numbers rather than validating or looking up real ones. It stops short of explicitly differentiating itself from near siblings such as finance-accountNumber or finance-iban, leaving that distinction to be inferred from the resource name.

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 or when-not-to-use guidance at all — no statement that this is for test/sample data, no warning against using the value for real transactions, and no pointer to a sibling for other finance identifiers. At best an agent infers from the word 'random' that this is a data-generation utility.

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