Skip to main content
Glama

Midway 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. Added
  10. Removed
  11. Added
  12. Removed
  13. Added
  14. Removed
  15. Added
  16. Removed
  17. 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"
+}
  18. Added
  19. Removed
  20. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already convey read-only and idempotent behavior. The description adds valuable context about the reconnect_url (reopens widget in UPDATE mode without disconnecting or consuming a connection slot) and bulk execution support, which are not captured in 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 well-structured and front-loaded. The first sentence packs in the core return values and behavior, followed by concise usage notes and a final line about bulk support. No filler or redundancy.

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 the lack of an output schema, the description adequately outlines the return structure (status, executionStatus, connector metadata, reconnect_url, and the `{ count, items }` shape for bulk calls). It covers primary usage patterns but omits edge cases such as error responses or pagination.

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?

The schema has zero description coverage. The description explains the semantics of `item` (single vs all) and `item_ids` (bulk), but leaves `item_id` undefined and does not clarify its relationship to `item`. This partial coverage leaves ambiguity for one of the three 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 identifies the tool's function: returning the current status of bank connections, with specific examples of statuses and additional data like executionStatus, connector metadata, and reconnect_url. It distinguishes itself from sibling tools like openfinance_list_connections by focusing on status and reconnect functionality.

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 clear usage context: omit `item` for all banks, pass `item` for a single bank, and use `item_ids` for bulk. However, it does not explicitly name alternative tools for when not to use this tool, or mention exclusion scenarios.

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

All Midway 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
Disambiguation3/5

The openfinance_* family is largely well-differentiated by resource and action, but the monolithic `marketplace` tool bundles search, invoke, install, billing, and prompt-library actions into one name, creating ambiguity about where platform capabilities live. Additionally, `openfinance_list_transactions` and `openfinance_list_transactions_by_item` both return transaction data and could be misselected despite their different aggregation intent.

Naming Consistency3/5

The openfinance_* tools consistently follow a clear verb_noun pattern, which gives the majority of the surface a predictable shape. But the generic platform tools mix bare verbs (`authenticate`, `connect`), nouns (`marketplace`, `toolkit_info`), and verb_noun names (`report_bug`, `show_version`), so the server has two naming dialects rather than one uniform convention.

Tool Count3/5

At 25 tools, this sits right at the top of the heavy range, and the server genuinely spans two broad domains: MCP platform administration and Open Finance banking data. The count is defensible given the breadth, but it is not a lean or easily navigable surface for an agent.

Completeness4/5

The Open Finance side is quite complete, covering connections, accounts, transactions, credit card bills, loans, investments, categories, provider status, sync, and disconnection. The platform side covers authentication, connection status, marketplace operations, bug reporting, and versioning, though some marketplace sub-actions are packed into one tool and bank connection itself is only reachable through URLs returned by other tools.

Resources