Skip to main content
Glama

Inter 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.3/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. The description adds useful behavioral details: what fields are returned (executionStatus, connector metadata, reconnect_url) and the specific behavior of the reconnect_url for re-authentication without consuming a slot. This goes beyond the annotations without contradiction.

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?

The description is somewhat lengthy but well-structured, front-loading the main purpose and then providing detailed behavior. It balances completeness with clarity, though could be slightly more concise.

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, the description adequately describes the return structure for both single and bulk modes. It covers the main fields and the reconnect_url functionality. Minor gaps like error handling or permissions are not critical for this read-only tool.

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?

The input schema has no descriptions (0% coverage), but the description compensates by explaining the effect of omitting `item` (returns all), passing `item` (single result), and using `item_ids` for bulk. This adds meaning beyond the schema alone.

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 with specific fields like UPDATED, UPDATING, LOGIN_ERROR, executionStatus, and reconnect_url. This differentiates it from sibling tools like openfinance_list_connections which list connections rather than providing detailed 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?

The description provides explicit guidance on usage: omit `item` to get all linked banks, pass `item` for a single bank, and accepts item_ids for bulk execution. It does not explicitly mention when not to use or compare to alternatives, but the usage patterns are clear.

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

All Inter 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/5.0
Disambiguation5/5

Each tool targets a distinct resource or action: the openfinance_* family cleanly separates accounts, transactions, bills, loans, investments, connections, sync, and provider health, while platform tools (authenticate, connect, marketplace, toolkit_info) cover different concerns. Even potentially similar pairs like get_item_status vs provider_status and list_transactions vs list_transactions_by_item are clearly differentiated by their descriptions.

Naming Consistency4/5

Open Finance tools follow a uniform openfinance_<verb>_<noun> snake_case pattern, and the generic tools are also readable English verbs/nouns (authenticate, connect, report_bug). The main inconsistency is that a few generic tools are bare nouns (marketplace, toolkit_info) while the rest are verbs, but the mix is predictable and never confusing.

Tool Count3/5

25 tools sit at the upper boundary of what is comfortable, and the set spans two distinct domains (Open Finance data access plus MCP platform/marketplace management). Each tool does appear to earn its place, but the count is heavy enough to feel borderline rather than optimally scoped.

Completeness5/5

The Open Finance surface is thorough: list/get for accounts, transactions, bills, loans, and investments, with sync, connection health, provider status, category correction, and disconnect all covered. The platform side also covers authentication, connection status, marketplace discovery/invocation, bug reporting, and version info, leaving no obvious dead ends for the stated purpose.

Resources