Skip to main content
Glama

Sicredi 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. 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"
+}
  8. Added
  9. Removed
  10. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint, idempotentHint, and destructiveHint false. Description adds behavioral details: returns specific fields, reconnect_url behavior (reopens widget in UPDATE mode without disconnecting), and bulk support. No contradiction.

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?

Two sentences, front-loaded with purpose, covering functionality and usage patterns efficiently. No 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?

Covers key aspects: return fields, usage modes, reconnect_url behavior, bulk support. Without an output schema, the description provides enough context for an AI agent to understand the tool's inputs and outcomes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has 0% description coverage. Description explains the main usage pattern (omit item for all, pass item for single, item_ids for batch). However, it does not differentiate between 'item' and 'item_id' explicitly, leaving some ambiguity.

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 explicitly states it returns the current status of a bank connection with specific fields like executionStatus, connector metadata, and reconnect_url. It clearly distinguishes single vs bulk operation, and among siblings it is unique as a status query tool.

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 instructions: omit 'item' for all banks, pass 'item' for single, and accepts item_ids for batched execution. Mentions reconnect_url use case. Lacks explicit when-not-to-use or comparison to siblings, but sufficient context is given.

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

All Sicredi 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

A3.9/5.0
Disambiguation3/5

Most openfinance_* tools have clearly distinct resource-action pairs, but several pairs overlap enough to cause misselection: authenticate vs connect, openfinance_list_accounts vs openfinance_get_accounts_detail, and openfinance_list_credit_card_bills vs openfinance_get_credit_card_bill. The long descriptions help, but the monolithic marketplace tool also mixes many sub-actions that overlap with report_bug and connection management.

Naming Consistency3/5

The openfinance_* tools mostly follow a consistent openfinance_<verb>_<noun> pattern, and the utility tools are all snake_case, but the conventions are mixed: marketplace is a bare noun, connect/authenticate are bare verbs, and openfinance_provider_status/toolkit_info lack a verb prefix. The pattern is readable but not uniform across the whole set.

Tool Count3/5

At 25 tools, this sits at the top of the borderline-heavy range. The Open Finance domain justifies many of them, but the marketplace mega-tool plus several overlapping list/get variants make the set feel larger than necessary.

Completeness4/5

The surface covers the full Open Finance lifecycle well: connection search/status/sync/disconnect, accounts, balances, transactions, credit card bills, loans, investments, and category correction. Minor gaps exist, such as no direct payment/transfer initiation or single-transaction detail endpoint, but these are outside the apparent read/aggregate purpose and are workable around.

Resources