Skip to main content
Glama

Dock MCP

by io.github.mcp-dir

openfinance_get_item_status

Read-onlyIdempotent

Returns the current status of a bank connection (UPDATED, UPDATING, LOGIN_ERROR, etc.), its executionStatus, connector metadata, and a reconnect_url that reopens the widget in UPDATE mode for that connection (re-authenticate / enter MFA token in place, without disconnecting and without consuming a connection slot). Omit item to get the status of ALL linked banks at once (returns { count, items }); pass item for a single bank.

Bulk support: accepts item_ids for batched execution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemNo
item_idNo
item_idsNo

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds valuable context about the reconnect_url behavior and the response structure ({ count, items } for all). 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loading the main purpose and parameter behavior. The first sentence is somewhat long but packs information efficiently without wasted words.

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?

Given 3 optional parameters and no output schema, the description adequately covers the return elements and the bulk versus single distinction. Minor gap: the response format for a single bank is only implied, not explicitly stated.

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 description coverage is 0%, so the description must compensate. It explains the use of `item` (single bank) and `item_ids` (bulk), but does not explain `item_id`, which is a separate parameter. This leaves a gap for one of the three parameters.

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?

The description clearly states the tool returns the status of one or all bank connections, including specific statuses, executionStatus, connector metadata, and reconnect_url. It differentiates between single and bulk retrieval, and the verb 'Returns' is specific to the resource 'status of a bank connection'. Among siblings, this is unique.

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?

The description provides clear context on when to omit vs include the `item` parameter for single vs all banks, and mentions bulk support via `item_ids`. However, it does not explicitly state when not to use this tool or suggest alternatives among siblings like `openfinance_list_connections`.

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

All Dock MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation4/5

Most openfinance_ tools target distinct resources (accounts, transactions, bills, loans, investments, connections, categories), so the core surface is clearly separated. However, several pairs could be confused at first glance: list_transactions vs list_transactions_by_item (both return transactions but at different scopes), get_credit_card_bill vs list_credit_card_bills (bill detail vs list of bills), and get_account_balance vs get_accounts_detail (balance snapshot vs full account object). The detailed descriptions help, but the overlap is nontrivial.

Naming Consistency4/5

The openfinance_* tools follow a consistent pattern (list_, get_, update_, search_, force_sync, provider_status, disconnect_bank), all using snake_case with a clear domain prefix. However, the general platform tools (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) have no such prefix or consistent verb_noun pattern, mixing the convention. The finance subset is strong, but the overall set isn't uniform.

Tool Count3/5

At 25 tools, this is at the upper boundary of acceptable for a broad financial domain covering connections, accounts, transactions, credit cards, loans, investments, categories, and provider health. Each tool adds real capability, so it doesn't feel bloated, but it's heavier than typical and pushes the borderline between well-scoped and too many.

Completeness4/5

The surface covers the Open Finance lifecycle thoroughly: connection management (list, reconnect, force sync, disconnect, provider status), account/balance reads, transaction listing (with filters, pagination, rich detail), credit card bills (closed and open/debt), loans, investments, category management, and a connector search. Obvious gaps like a tool for creating connections are handled via widget URLs rather than an API call, so the coverage feels adequate. Minor gaps exist (e.g., no explicit tool for updating a connection's credentials beyond reconnect URLs), but nothing that would block core workflows.

Resources