Skip to main content
Glama

Crefisa MCP

by io.github.mcp-dir
OverviewAdmin

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. 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"
+}
  4. Added
  5. Removed
  6. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds behavioral details: returns executionStatus, connector metadata, and reconnect_url (which reopens widget in UPDATE mode for re-authentication without disconnecting or consuming a slot). Bulk execution behavior is also described. 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?

Concise single paragraph, front-loaded with core function. Efficiently covers key behavior, parameters, and bulk support. No fluff.

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?

No output schema, but description lists return fields (status, executionStatus, connector metadata, reconnect_url) and format for bulk (`count`, `items`). Provides sufficient context for a read status tool, including widget behavior detail.

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 has 0% description coverage; description explains `item` (optional, scope control) and `item_ids` (bulk), but does not clarify `item_id` parameter (singular vs plural distinction missing). Partially compensates for lack of schema descriptions but could be more precise.

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?

Description clearly states it returns bank connection status with specific fields like UPDATED, UPDATING, LOGIN_ERROR, executionStatus, connector metadata, and reconnect_url. It distinguishes between fetching all banks (omit `item`) vs a single bank (pass `item`), and mentions bulk support via `item_ids`. This differentiates it from sibling tools like `openfinance_list_connections` (which lists connections) or `openfinance_provider_status` (provider status).

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 guidance on when to use `item` parameter vs omitting it, and mentions bulk support for `item_ids`. It does not explicitly state when not to use this tool or compare to alternatives, but the context is sufficient for an agent to decide.

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

All Crefisa 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.

Resources