Skip to main content
Glama

Bradescard 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. 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"
+}
  12. Added
  13. Removed
  14. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Adds details beyond annotations: explains returned fields (executionStatus, connector metadata, reconnect_url), behavior for missing item, and bulk support. No contradiction with annotations (readOnlyHint, idempotentHint).

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?

Single paragraph with front-loaded main purpose. Every sentence adds value, though could be slightly more structured (e.g., bullet points for modes). Still concise and clear.

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 explains return format for both single and bulk modes. Covers essential behavior. Could mention error handling, but sufficient for a status check tool.

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?

Describes 'item' and 'item_ids' well, but 'item_id' in the schema is not mentioned. With 0% schema coverage, description should cover all parameters; it partially does but misses one.

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?

Clearly states it returns the status of a bank connection with specific status values. Distinguishes between single and bulk modes, and references a reconnect_url. Differentiates from sibling tools like openfinance_list_connections.

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?

Explains when to omit item (all banks) vs pass item (single bank), and mentions bulk support with item_ids. Does not explicitly exclude scenarios, but the context is clear. Could note alternatives like openfinance_list_connections.

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

All Bradescard 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.2/5.0
Disambiguation4/5

Most tools are highly distinct, targeting different resources (accounts, transactions, bills, loans, investments, connections). However, openfinance_list_transactions and openfinance_list_transactions_by_item both return transaction data with different scopes, which could cause misselection. Also openfinance_get_item_status vs openfinance_provider_status are distinct but similar in name.

Naming Consistency5/5

The openfinance_* tools follow a consistent verb_noun pattern (list_accounts, get_credit_card_bill, force_sync). Generic tools (authenticate, connect, marketplace) are also clearly named and consistent within their own domain. No mixed conventions or chaotic naming.

Tool Count4/5

At 25 tools, the server is on the heavier side (borderline of the 16-25 range) but each tool serves a clear purpose in the open finance domain, covering multiple resource types and auxiliary functions like marketplace and status. A slight trim could be made (e.g., merging some list/get pairs), but it's not excessive.

Completeness4/5

The server covers the full read lifecycle for accounts, transactions, bills, loans, and investments, plus connection management (list, disconnect, force sync) and category updates. Minor gaps like lack of direct deletion for financial records are acceptable since those are not typical operations. The generic tools (marketplace, auth, version) round out the toolkit.

Resources