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?
Annotations already indicate destructiveHint=true. The description adds that the bank's data will no longer be available and that it returns an add_connection_url, providing useful behavioral context beyond annotations. No contradictions.
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?
Two short sentences, front-loaded with the core action and consequences. No unnecessary words or redundancy.
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 tool with one parameter and no output schema, the description covers the core action and result. However, it omits details about parameter format, error conditions, and prerequisites, leaving gaps for an AI agent to use it correctly.
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?
Schema coverage is 0%, and the description does not explain the sole required parameter 'item'. It only says 'for a specific bank' without specifying the parameter's meaning (likely an identifier). This fails to compensate for the lack of schema documentation.
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?
The description clearly states it revokes consent and deletes connection data for a specific bank, with a result that data is no longer available and returns a re-connection URL. This distinguishes it from sibling tools like openfinance_force_sync or openfinance_get_item_status.
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?
The description implies usage when disconnecting a bank but lacks explicit when-to-use or when-not-to-use guidance. No alternatives are mentioned, and prerequisites (e.g., having an active connection) are not stated.
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 openfinance_* tools are mostly separated by resource (accounts, bills, loans, investments, connections), and the meta tools are distinct. The main ambiguities are openfinance_list_transactions vs openfinance_list_transactions_by_item, and openfinance_get_credit_card_bill vs openfinance_list_credit_card_bills, though their descriptions do clarify different intents.
The openfinance_* family follows a consistent verb_noun pattern, and the generic platform tools use bare lowercase names like connect, authenticate, and marketplace. The mixed prefixes and the occasional singular/plural variation (get_credit_card_bill vs list_credit_card_bills) make the overall namespace readable but not fully uniform.
25 tools is at the heavy end and combines two distinct areas: platform/meta tooling and a deep Open Finance adapter. Most openfinance tools are justifed by real endpoints, but the count feels bulky for an agent to browse, and the marketplace tool packs an unusually large number of capabilities into a single entry.
The Open Finance surface is unusually complete: accounts, balances, transactions, credit-card bills, loans, investments, connection status, force sync, provider status, category correction, and disconnect are all present. The platform side is also broad via marketplace and toolkit_info, with only minor granularity gaps such as no dedicated get-single-transaction tool or separate marketplace sub-tools.