Skip to main content
Glama

Toro 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.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive. The description adds meaningful behavioral context: reconnect_url reopens the widget in UPDATE mode without disconnecting or consuming a connection slot, and returns various status values. This exceeds what annotations provide, though it does not cover all edge cases.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

The description is well-structured with the main behavior, then usage patterns, then bulk support. Every sentence adds useful information without redundancy. It is appropriately concise given the tool's complexity.

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?

The description covers the main return values (status, executionStatus, connector metadata, reconnect_url) and the bulk response shape. It lacks details on `item_id` semantics and any error conditions, but is otherwise complete for a read-only tool with no output schema.

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 coverage is 0%, so description must compensate. It explains `item` (single bank) and `item_ids` (batch), but does not explain `item_id` or its relationship to `item`. This is a partial gap in parameter meaning.

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 it returns the current status of a bank connection, including specific fields like executionStatus, connector metadata, and reconnect_url. It distinguishes from sibling tools by describing a unique resource and operation, and mentions bulk support via item_ids.

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?

Provides clear context on when to omit or pass `item` for single vs. all banks, and mentions bulk support. However, it does not explicitly compare with alternatives like openfinance_list_connections or openfinance_provider_status, so no exclusions or when-not-to-use guidance.

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

All Toro 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.1/5.0
Disambiguation4/5

Each Open Finance resource has a clearly named list/get pair, and connection status vs provider status vs force sync are distinct. The main ambiguity is between list_accounts (which already carries balances) and get_account_balance, and between list_transactions and list_transactions_by_item, which requires reading the descriptions carefully.

Naming Consistency4/5

The openfinance_* tools follow a consistent verb_noun pattern (list_*, get_*, update_*, force_sync, search_*). Exceptions like marketplace, toolkit_info, and openfinance_provider_status break the pattern slightly, but the two logical groups are predictable internally.

Tool Count3/5

At 25 tools this is on the heavy end of the scale. Most tools have a real purpose, but several list/get pairs and the multi-purpose marketplace mega-tool could be consolidated without losing functionality, making the overall surface feel larger than strictly necessary.

Completeness4/5

The Open Finance surface is impressively broad: connections, accounts, balances, transactions, credit-card bills, loans, investments, categorization, sync, provider health, and connector search are all covered. Minor gaps like a single-transaction getter or a consolidated statement export force agents to assemble data with extra calls, but no critical workflow is blocked.

Resources