iso20022-bank-profile-mcp

List clearing profiles

list_profiles

Read-onlyIdempotent

Discover available ISO 20022 clearing profiles as lightweight summaries to find valid profile IDs before fetching rules or linting payloads.

Instructions

List the available clearing profiles as lightweight summaries.

Purpose:
    Discover and enumerate all built-in and registered ISO 20022 clearing
    profiles, including supported messages and rule counts.

When to use:
    Call this tool first to discover valid `profile_id` values before
    fetching full profile rules with `get_profile` or linting payloads
    with `lint_payload`.

When NOT to use:
    Do not use if you need full rule bodies and validation expressions;
    use `get_profile` instead.

Behavioral transparency:
    - Deterministic: Returns identical summaries for registered profiles.
    - External dependencies: None (reads internal registry).
    - Side effects: Pure read-only operation; modifies no state.
    - Error states: Always succeeds and returns a list.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.2Jul 29, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds genuinely new context: determinism across calls, no external dependencies (reads internal registry), and the error state ('always succeeds and returns a list'). Some lines restate the annotations rather than extend them, which keeps it short of a 5.

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?

Well front-loaded: the one-line summary precedes the Purpose/When-to-use/When-NOT-to-use/Behavior sections, and the routing advice appears early. The behavioral section is somewhat long and partially duplicates the annotations, which is minor redundancy rather than padding.

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?

An output schema exists, so the description need not describe the return shape, and the tool is a parameterless read-only list. An agent has everything needed: purpose, correct call ordering, the sibling to fall back to, and the guarantee of success.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline is 4. The description references profile_id values only as outputs to discover, not as inputs, which is consistent with the empty schema.

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?

States a specific verb and resource ('List the available clearing profiles as lightweight summaries') and scopes it to built-in and registered ISO 20022 clearing profiles, including what the summaries contain (supported messages, rule counts). It is clearly distinguishable from get_profile, which returns full rule bodies.

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?

Explicitly prescribes when to call it ('Call this tool first to discover valid profile_id values before fetching full profile rules with get_profile or linting payloads with lint_payload') and when not to ('Do not use if you need full rule bodies...; use get_profile instead'). It names the sibling alternatives and the condition that selects them.

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

Deploy Server