Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

finance-iban

Generate random IBANs for testing or sample financial data, with optional country code and formatted output.

Instructions

Generates a random IBAN.

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-iban"
  }
}

Input Schema

NameRequiredDescriptionDefault
formattedNoReturn a formatted version of the generated IBAN.
countryCodeNoThe country code from which you want to generate an IBAN.

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 provided, so the description carries the full burden of behavioral disclosure. It states only that the output is random and does not explain whether the generated IBAN is syntactically valid, whether it is a real or fake account identifier, whether it has side effects, or what the return value looks like.

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?

The description is a single clear sentence with no filler or repetition. It is appropriately front-loaded, though its brevity leaves important behavioral details unstated.

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 generator tool with no annotations and no output schema, the description is too sparse. It does not explain the output format, whether the IBAN is valid or merely random, how countryCode defaults or behaves, or any safety or authenticity caveats.

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 input schema already documents both optional parameters: formatted and countryCode. The description adds no additional meaning about how countryCode affects generation or what formatting entails, so the baseline score 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 uses a specific verb and resource: "Generates a random IBAN." This clearly identifies the tool's core action, though it does not distinguish it from sibling finance tools such as finance-accountNumber or finance-bic.

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 guidance on when to use this tool, when not to use it, or how it relates to alternatives. It also does not mention whether it is intended for test data, validation, or production use.

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