list_banksRetrieve banks available in a country via Enable Banking, including maximum consent length, to identify the exact bank name needed for starting a consent.
Banks available through Enable Banking in a country, with the maximum consent length. Use the exact name with start_consent.
| Name | Required | Description | Default |
|---|---|---|---|
| search | No | Filter by (part of) the bank name | |
| country | No | ISO country code, default DK |
Changes observed during successful MCP inspections.
v0.1.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, and the description implies a read-only listing operation but does not explicitly state side effects, safety, or ordering/pagination behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise, front-loaded with the core purpose, and includes a practical pointer for using the returned bank name with start_consent.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple listing tool with no output schema, the description gives enough information about what is returned and how to use it downstream.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already fully describes the search and country parameters with defaults, so the description adds little semantic value beyond what is provided.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states the tool lists banks available through Enable Banking in a country and includes maximum consent length. This distinguishes it from sibling list tools like list_accounts and list_watches.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides workflow context by telling the agent to use the exact bank name with start_consent, but does not explicitly compare against alternative tools or state when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.