Skip to main content
Glama

Swiss Clearing Lookup

lookup_ch_clearing
Read-onlyIdempotent

Resolve a Swiss BC-Nummer / IID (1 to 5 digits) into the underlying institution. USE WHEN: the user mentions a Swiss bank by BC-Nummer or IID, pastes a CH or LI IBAN clearing code, asks routing details for a Swiss instant transfer (SIC, euroSIC), asks about QR-bill QR-IID resolution, or needs to classify a Swiss financial institution (bank vs PFS vs SIC-only participant). EVERY IID OF THE SIX BANKMASTER, with its full payment-rail participation (SIC, RTGS CHF, Instant Payments CHF, euroSIC, LSV+/BDD) plus QR-IID allocation, not just a name lookup. BACKED BY: 1,100+ SIX BankMaster entries (Swiss official source, re-read weekly). RETURNS: institution { name, type, iid_type, headquarters_iid }, address, bic, payment_services { sic, rtgs_chf, instant_payments_chf, eurosic, lsv_bdd_chf, lsv_bdd_eur }, sic_iid, qr_iid, valid_on. Only relevant for CH and LI accounts. COST: $0.003 per call (free with no key on this transport: 25 units a week per source address, one per call and one per IBAN in batch_validate_iban, reset on Monday 00:00 UTC. Or an ifk_ key with no e-mail at all: POST https://api.ibanforge.com/v1/keys/generate with no body for 25 calls/month, on the REST API or on this transport, and POST /v1/keys/claim lifts that same key to 200 a month. Send the key here as Authorization: Bearer ifk_… (or X-API-Key) and each call counts against it exactly as on the REST API).

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": {
      "iid": "<iid>"
    },
    "name": "lookup_ch_clearing"
  }
}

Input Schema

NameRequiredDescriptionDefault
iidYesSwiss IID (1-5 digit number)

Output Schema

NameRequiredDescriptionDefault
bicNoBIC if mapped.
iidNoNormalized 5-digit BC-Nummer.
noteNo
errorNo
foundNo
qr_iidNoQR-bill enabled IID.
addressNo
messageNo
qr_iidsNoEvery QR-IID SIX allocates to the institution, present only when there is more than one; qr_iid carries the lowest.
sic_iidNo
valid_onNo
cost_usdcNoWhat THIS call was billed. Zero on the free MCP tier.
is_qr_iidNoPresent (true) only when the IID asked about is a QR-IID (SIX QR-bill range 30000-31999); iid then carries the standard IID of the institution and qr_iid the QR-IID asked about.
institutionNo
qr_iid_sourceNoHow qr_iid was obtained. register = SIX BankMaster publishes this pairing; headquarters = inherited from the head office (headquarters_iid), an inference and not a published SIX pairing. Null when qr_iid is null.
list_price_usdcNoCatalogue price of the same call on the paid REST/x402 route.
redirected_fromNo
state_guaranteeNoPresent for the 24 Swiss cantonal banks only, matched by head-office IID; a branch or QR-IID takes its head office's entry. A description of the institution, not an assessment of the bank or of any account.
payment_servicesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedOutput schema / properties / is_qr_iid
      Added value: +{
      +  "description": "Present (true) only when the IID asked about is a QR-IID (SIX QR-bill range 30000-31999); iid then carries the standard IID of the institution and qr_iid the QR-IID asked about.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / qr_iid_source
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "register",
      +        "headquarters"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "How qr_iid was obtained. register = SIX BankMaster publishes this pairing; headquarters = inherited from the head office (headquarters_iid), an inference and not a published SIX pairing. Null when qr_iid is null."
      +}
    • addedOutput schema / properties / qr_iids
      Added value: +{
      +  "description": "Every QR-IID SIX allocates to the institution, present only when there is more than one; qr_iid carries the lowest.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / state_guarantee
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Present for the 24 Swiss cantonal banks only, matched by head-office IID; a branch or QR-IID takes its head office's entry. A description of the institution, not an assessment of the bank or of any account.",
      +  "properties": {
      +    "as_of": {
      +      "description": "The day the text was read (YYYY-MM-DD).",
      +      "type": "string"
      +    },
      +    "canton": {
      +      "description": "Two-letter canton code.",
      +      "type": "string"
      +    },
      +    "guaranteed": {
      +      "description": "True when the cantonal law makes the canton liable for the bank's liabilities where the bank's own funds fall short (Staatsgarantie, garantie de l'État).",
      +      "type": "boolean"
      +    },
      +    "note": {
      +      "description": "Present where the guarantee ended (BEKB, BCGE: what the law kept and until when) or where the law has none (BCV).",
      +      "type": "string"
      +    },
      +    "source": {
      +      "description": "The law, its number in the cantonal collection, and the article. The exclusions the law writes (for example subordinated debt) are in that law; where they sit in another article, that article is cited too.",
      +      "type": "string"
      +    },
      +    "url": {
      +      "description": "The text that was read.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "guaranteed",
      +    "canton",
      +    "source",
      +    "url",
      +    "as_of"
      +  ],
      +  "type": "object"
      +}
  2. Changed14 schema fields changed
    • removedOutput schema / properties / address / properties / building_number / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / address / properties / building_number / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / address / properties / post_code / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / address / properties / post_code / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / address / properties / street / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / address / properties / street / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / address / properties / town / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / address / properties / town / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / bic / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / bic / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / qr_iid / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / qr_iid / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / sic_iid / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / sic_iid / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  3. Changed2 schema fields changed
    • addedOutput schema / properties / cost_usdc / description
      Added value: +"What THIS call was billed. Zero on the free MCP tier."
    • addedOutput schema / properties / list_price_usdc
      Added value: +{
      +  "description": "Catalogue price of the same call on the paid REST/x402 route.",
      +  "type": "number"
      +}
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "address": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "building_number": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        },
      +        "country": {
      +          "type": "string"
      +        },
      +        "post_code": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        },
      +        "street": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        },
      +        "town": {
      +          "anyOf": [
      +            {
      +              "type": "string"
      +            },
      +            {
      +              "type": "null"
      +            }
      +          ]
      +        }
      +      },
      +      "required": [
      +        "street",
      +        "building_number",
      +        "post_code",
      +        "town",
      +        "country"
      +      ],
      +      "type": "object"
      +    },
      +    "bic": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "BIC if mapped."
      +    },
      +    "cost_usdc": {
      +      "type": "number"
      +    },
      +    "error": {
      +      "type": "string"
      +    },
      +    "found": {
      +      "type": "boolean"
      +    },
      +    "iid": {
      +      "description": "Normalized 5-digit BC-Nummer.",
      +      "type": "string"
      +    },
      +    "institution": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "headquarters_iid": {
      +          "type": "string"
      +        },
      +        "iid_type": {
      +          "description": "headquarters | branch | other",
      +          "type": "string"
      +        },
      +        "name": {
      +          "type": "string"
      +        },
      +        "type": {
      +          "description": "bank | cantonal_bank | postfinance | raiffeisen | central_bank | foreign_participant",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "name",
      +        "type",
      +        "iid_type",
      +        "headquarters_iid"
      +      ],
      +      "type": "object"
      +    },
      +    "message": {
      +      "type": "string"
      +    },
      +    "note": {
      +      "type": "string"
      +    },
      +    "payment_services": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "eurosic": {
      +          "type": "boolean"
      +        },
      +        "instant_payments_chf": {
      +          "type": "boolean"
      +        },
      +        "lsv_bdd_chf": {
      +          "type": "boolean"
      +        },
      +        "lsv_bdd_eur": {
      +          "type": "boolean"
      +        },
      +        "rtgs_chf": {
      +          "type": "boolean"
      +        },
      +        "sic": {
      +          "description": "Swiss Interbank Clearing.",
      +          "type": "boolean"
      +        }
      +      },
      +      "required": [
      +        "sic",
      +        "rtgs_chf",
      +        "instant_payments_chf",
      +        "eurosic",
      +        "lsv_bdd_chf",
      +        "lsv_bdd_eur"
      +      ],
      +      "type": "object"
      +    },
      +    "qr_iid": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "QR-bill enabled IID."
      +    },
      +    "redirected_from": {
      +      "type": "string"
      +    },
      +    "sic_iid": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "valid_on": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  5. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well past the readOnly/idempotent annotations by disclosing data provenance and freshness (1,100+ SIX BankMaster entries, re-read weekly), coverage breadth (all six BankMaster IIDs, full payment-rail participation), rate limits (25 units/week per source address, Monday 00:00 UTC reset), and auth handling (Authorization: Bearer ifk_… or X-API-Key).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose, USE WHEN, coverage and RETURNS blocks are well front-loaded and information-dense. However, the COST section is a long run-on sentence with nested parentheses containing key-generation URLs and quota arithmetic that crowds out tool-selection information and makes the definition hard to scan.

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

Completeness5/5

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

Everything an agent needs is present: what it resolves, when to call it, what the returned fields are (institution, address, bic, payment_services, sic_iid, qr_iid, valid_on), geographic applicability, and cost constraints. An output schema and annotations exist, so the description need not go further.

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 100% and the single 'iid' property already documents 'Swiss IID (1-5 digit number)'; the description only restates the 1-to-5-digit constraint. No additional semantics (e.g. leading zeros, padding, error behavior for unknown IIDs) are added, so the 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?

Opens with a specific verb and resource: 'Resolve a Swiss BC-Nummer / IID ... into the underlying institution', and spells out the mapping direction. It clearly differs from siblings like lookup_bic, validate_iban or check_swiss_qr_bill by naming the clearing-code resource and the institution-resolution output.

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

Usage Guidelines5/5

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

The 'USE WHEN' block enumerates concrete triggers (BC-Nummer/IID mention, CH/LI IBAN clearing code, SIC/euroSIC routing questions, QR-IID resolution, bank vs PFS classification). It also states the negative scope: 'Only relevant for CH and LI accounts'.

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.