Skip to main content
Glama

Atacadão 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.4/5.0
Behavior5/5

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

Annotations already indicate readOnly, idempotent, non-destructive. The description adds valuable behavioral context: the reconnect_url reopens the widget in UPDATE mode without disconnecting or consuming a slot, and explains return format for both single and bulk queries. 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.

Conciseness5/5

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

The description is three sentences, each carrying essential information: what is returned, how to use for single/all, and bulk support. No redundant text, front-loaded with key details.

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 no output schema and three optional parameters, the description covers return values for single and all modes, bulk support, and behavioral traits. It doesn't explain error handling or parameter relationships (e.g., item vs item_id), but is largely complete for a read-only tool.

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 'item' and 'item_ids' but does not mention 'item_id', leaving its purpose ambiguous. While it adds meaning for two parameters, the third is underexplained.

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 current status of a bank connection, including specific fields like executionStatus and reconnect_url. It distinguishes single vs. all banks and mentions bulk support, making the purpose very specific compared to sibling tools.

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 explains when to use the tool (get status) and provides usage instructions for different cases: omit item for all, pass item for single, and bulk via item_ids. It does not explicitly mention when not to use or alternatives, but the context is clear.

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

All Atacadão 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

Tools are largely distinct: openfinance_* tools cover specific resources (accounts, transactions, bills, loans, investments) with clear boundaries. Some overlap exists between list_transactions and list_transactions_by_item, and between status/sync tools (get_item_status, force_sync, provider_status), but descriptions are detailed enough to guide selection.

Naming Consistency4/5

The openfinance_* prefix provides strong consistency for the bulk of tools, with clear verb_noun patterns (list, get, update, force_sync). The platform tools (authenticate, connect, marketplace, report_bug, etc.) break the pattern but are few and their names are intuitive. Overall, minor mixing of conventions but readable.

Tool Count4/5

25 tools is on the higher side but appropriate for a comprehensive Open Finance and platform management server. The count includes both data access (accounts, transactions, bills, loans, investments) and platform utilities (authentication, connection state, marketplace). No redundant tools; each serves a clear purpose.

Completeness4/5

The surface covers the core read operations for connected banks (accounts, transactions, bills, loans, investments), connection management (sync, status, disconnect), and category correction. Minor gaps include no get-transaction-by-id and no update for account metadata, but these are not critical for the typical use case of a banking data aggregator.

Resources