Skip to main content
Glama

CoinVet

Validate a BIC / SWIFT code format

bic_validate
Read-onlyIdempotent

Validate a BIC/SWIFT code's structure (bank code, ISO country, location, optional branch) and flag test BICs. Format check only, not a directory lookup.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "bic": "<bic>"
    },
    "name": "bic_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
bicYesBIC/SWIFT code (8 or 11 chars)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety and purity are covered. The description adds real behavioral content beyond that: it discloses that test BICs are flagged and that no directory/registry lookup occurs, which matters for interpreting results. It stops short of saying what a failure response contains.

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?

One sentence with zero filler, front-loading the action and the validated components before the scoping exclusion. Nothing could be removed without losing information.

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

Completeness4/5

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

For a simple one-parameter validator with no output schema, the description covers what is checked, what is not, and one notable side behavior (test BIC flagging). The only gap is that it doesn't indicate the shape of the result, which matters slightly for a validation tool an agent must branch on.

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?

With a single parameter at 100% schema coverage, the schema already states the BIC must be 8 or 11 characters. The description's mention of the structural components adds interpretive meaning about what each segment is, but it introduces no format or syntax detail the schema lacks. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (validate) and resource (BIC/SWIFT), and enumerates exactly what structural parts are checked: bank code, ISO country, location, optional branch. The closing clause scopes it away from directory lookup, so an agent can tell it apart from a resolution service without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Format check only, not a directory lookup" is an explicit when-not statement that prevents the agent from expecting bank-name resolution. It does not name a sibling alternative for lookup-style needs, so it stops short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources