Skip to main content
Glama

Parse BIC identifier structure

bpj_bic_structure
Read-onlyIdempotent

Check eight- or eleven-character syntax and separate institution, country, location and branch fields.

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": {
      "value": "<value>"
    },
    "name": "bpj_bic_structure"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this read-only, idempotent, closed-world and non-destructive, so safety is covered. The description adds the field decomposition, which tells the agent what work is being performed, but it says nothing about behavior on a malformed value — whether it errors, returns null fields, or reports a validity flag — and no output schema exists to fill that gap.

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 sentence, front-loaded with the length check before the field split, with no filler. The compression is slightly aggressive for a single sentence carrying both a validation and a decomposition promise.

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?

The tool is simple (one required parameter, no nesting, no output schema), so the description is close to sufficient, but with no output schema the caller still cannot tell what shape the separated fields take or what a failed check looks like. That is the one material gap for a parsing tool.

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 coverage is 0% (the only property is documented as 'Input value'), so the description must compensate, and it partly does by implying the parameter is the BIC string with an 8- or 11-character shape. It still leaves case sensitivity, allowed characters, and whether an omitted branch field is normalized or returned empty 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?

The description names a concrete operation (syntax check) and a concrete output (institution, country, location and branch fields separated from the code), and the 8-vs-11-character constraint pins down the identifier family. It is clear without opening the schema, though it never differentiates itself from a sibling like bpj_dq_identifier_shape.

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 statement of when to reach for this tool versus an alternative, and no preconditions (e.g., confirm the value is a BIC rather than an IBAN or LEI). The only hint is the syntax constraint, which a caller must infer as the applicability test.

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.