Skip to main content
Glama
Faker MCP Server

Faker MCP Server

by kentrino

finance-bic

Generates a random SWIFT/BIC code in ISO-9362 format, optionally adding a three-digit branch code for test data and validation scenarios.

Instructions

Generates a random SWIFT/BIC code based on the ISO-9362 format.

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

Input Schema

NameRequiredDescriptionDefault
includeBranchCodeNoWhether to include a three-digit branch code at the end of the generated code.

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 provided, so the description carries the full burden. It usefully discloses that output is randomly generated and follows ISO-9362, but says nothing about determinism, seeding, uniqueness guarantees, or whether the result is a plain string versus a structured object.

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?

One well-formed sentence with the key qualifier ('random') and standard ('ISO-9362') front-loaded; no wasted wording. It is lean but leaves the reader wanting one more clause about output shape.

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?

For a trivial one-optional-parameter generator this is mostly adequate, but with no output schema and no annotations the description should state what is returned (a string, format length, whether branch code appears by default). Those gaps are small but real for an agent consuming the result.

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 optional parameter, so the schema already explains includeBranchCode fully. The description adds no additional meaning about default behavior or how the branch code is chosen, which is the baseline-3 case.

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 SWIFT/BIC code') plus the format standard (ISO-9362), which clearly separates it from siblings like finance-iban or finance-accountNumber. It does not explicitly contrast with the nearest sibling generator, keeping it just short of a 5.

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, and no mention of alternatives such as finance-iban for IBAN generation. The word 'random' only implicitly hints at test-data/synthetic-value usage; an agent must infer the context entirely.

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