swissco

Official

Overview Schema Source Related Servers Discussions Admin

swissco_finma

Read-onlyIdempotent

Look up institutions on FINMA's authorised banks and securities firms list. Filter by name, city, licence type, or category; fetch a single record by UID.

Instructions

Institutions on FINMA's list of authorised banks and securities firms.

Each row carries name, city, licence_type, supervisory_category, uid, foreign_control, no_securities_firm_activity, non_account_holding_securities_firm and about_to_cease_operations.

This one list covers banks and securities firms. Insurers, portfolio managers and fund management companies hold their authorisations on other FINMA lists, so a company absent here may still be supervised. FINMA also publishes some authorised institutions with no UID, which no UID lookup can reach.

Both published files are cached under the state directory for a day, so the first call in a day is the slow one.

Input Schema

TableJSON Schema

Name	Required	Description
`uid`	No	One institution by UID.
`limit`	No	Maximum rows.
`query`	No	Text to match in the institution's name or city.
`category`	No	FINMA supervisory category, 1 to 5. 1 is the largest.
`licence_type`	No	Bank, Securities firm, Foreign bank branch office, or Foreign securities firm branch office.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`rows`	Yes
`count`	Yes
`notes`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Sep 11, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover readOnly/openWorld/idempotent, so the bar is lower, and the description still adds genuinely useful operational context: both files are cached for a day and the first call of the day is slow, and some institutions carry no UID and cannot be reached by UID lookup. This is real behavior beyond the annotations.

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?

Purpose is front-loaded and each section (fields, scope, caveats, caching) is a distinct, non-redundant block. The medium-length field enumeration partially duplicates the output schema, which keeps it from a full 5.

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?

With an output schema present, return values need not be explained, and the description still supplies scope limits, the no-UID gap, and caching latency. It is complete enough for an agent to call correctly; the only omission is any routing pointer to a sibling for the excluded institution types.

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%, so the schema already documents uid, limit, query, category and licence_type. The description adds no new parameter meaning (the licence-type examples live in the schema), so the baseline 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 first sentence names a specific resource (FINMA's list of authorised banks and securities firms) and the enumerated row fields make the scope concrete. It is distinguishable from data-source siblings like swissco_lei, but it never names an alternative, so it stops short of 5.

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?

It clearly states the boundary condition: this list covers banks and securities firms only, while insurers, portfolio managers and fund managers are on other FINMA lists, so absence here does not imply unsupervised. That is a strong 'when it applies and when it does not' signal, but no sibling tool is named as the alternative for the excluded cases.

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

Deploy Server