Skip to main content
Glama

Stone Pagamentos 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

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Added
  6. Removed
  7. Added
  8. Removed
  9. Changed2 schema fields changed
    • addedInput schema / properties / item_id
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / item_ids
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  10. Added
  11. Removed
  12. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, and non-destructive hints. The description adds valuable behavioral details beyond these, such as the reconnect_url's effect of reopening the widget in UPDATE mode without disconnecting or consuming a connection slot, and the bulk execution behavior. No contradiction with annotations.

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 front-loaded with the primary return value, then covers all-bank vs. single-bank usage and bulk support in just three sentences. Every sentence adds unique value with no filler or repetition.

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?

Despite no output schema, the description outlines the return fields and explains key behaviors (reconnect, bulk, all vs. single). The missing `item_id` parameter and lack of error-handling notes are minor gaps, but the overall context is strong for a read-only tool with good annotations.

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 the description must compensate. It explains `item` and `item_ids` well, but completely omits `item_id`, leaving its purpose ambiguous. This is a clear gap, though the description does provide meaningful semantics for the main 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 current status of a bank connection, listing specific fields (status, executionStatus, connector metadata, reconnect_url). It distinguishes this from sibling list tools by emphasizing status and re-authentication details, and it explicitly differentiates single vs. all-bank behavior.

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 usage context: omit `item` for all banks, pass `item` for a single bank, and use `item_ids` for bulk. It does not explicitly name alternatives or exclusion conditions, but the parameter-based usage guidance is strong enough to guide an agent.

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

All Stone Pagamentos 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

Most tools have clearly distinct purposes, especially within the openfinance_* group (list vs get vs sync vs status). A few potential overlaps exist (e.g., openfinance_list_transactions vs openfinance_list_transactions_by_item, openfinance_get_account_balance vs openfinance_list_accounts), but descriptions are detailed enough to guide correct selection.

Naming Consistency4/5

The openfinance_* tools follow a consistent verb_noun pattern (e.g., openfinance_list_accounts, openfinance_get_item_status). However, non-openfinance tools (authenticate, connect, marketplace, toolkit_info) use a different style, and one tool (openfinance_list_transactions_by_item) breaks the pattern slightly. Overall readable and predictable within the primary domain.

Tool Count3/5

With 25 tools, the count is on the heavy side per the calibration rubric (16-25 feels heavy). The server covers a broad financial data domain, which justifies the number, but it may present a steep learning curve and potential overwhelm for agents.

Completeness4/5

The tool surface is comprehensive for read-only Open Finance data access: accounts, transactions, balances, bills, loans, investments, category management, connection lifecycle, and status monitoring. Minor gaps exist (e.g., no direct payment initiation, no investment transaction creation), but for the stated purpose of data and analysis, coverage is strong.

Resources