Revokes the Open Finance consent for a specific bank and deletes the connection data. The bank's data will no longer be available. Returns an add_connection_url to re-connect if needed.
| Name | Required | Description | Default |
|---|---|---|---|
| item | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Adds beyond annotations: confirms data removal and return of re-connect URL. DestructiveHint already indicates mutation.
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?
Three concise sentences covering action, consequence, and return value. No redundant information.
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?
Adequate for a simple destructive tool but missing parameter explanation. Lacks output schema details.
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?
No documentation for the 'item' parameter. Schema coverage is 0%, and description fails to explain what 'specific bank' means or how to obtain the value.
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?
Clear verb (revokes/deletes) and specific resource (bank connection). Distinguishes from sibling tools like listing or getting balance.
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?
Implied usage: disconnect a bank. No explicit when-to-use or alternatives. Lacks prerequisites like checking item status first.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The Open Finance tools have clear list/get pairs for each resource (accounts, transactions, loans, investments, bills), but the marketplace tool is a monolith combining search, describe, invoke, install, subscribe, and prompt library actions, causing ambiguity about which action to use. Additionally, openfinance_list_transactions and openfinance_list_transactions_by_item overlap in purpose but are distinguished by scope.
The openfinance_* group follows a consistent verb_noun pattern (list, get, update, force_sync, etc.), but the platform tools (authenticate, connect, marketplace, show_version, report_bug, toolkit_info) use mixed bare verbs and nouns, creating two distinct conventions. Names like openfinance_list_transactions_by_item are longer but still consistent within the group.
25 tools is at the heavy end, but the Open Finance domain alone justifies 17 tools covering distinct resources and operations. The platform tools add 8 more, though the marketplace tool bundles many sub-actions into one, inflating the effective count. The number is borderline but not excessive given the breadth of banking functionality.
The Open Finance surface is comprehensive with list/get for every major resource, plus support for sync, status, search, categories, and category updates. The platform tools cover authentication, connection status, marketplace operations, bug reporting, version, and toolkit state. No obvious gaps or dead ends in the workflow.