Skip to main content
Glama

Monte Bravo MCP

by io.github.mcp-dir

openfinance_force_sync

Forces the bank to re-sync one or more connections NOW and WAITS for it to finish (PATCH /items/:id, then polls until the item stops updating, up to ~60s). Use this when a balance or transaction list looks stale: a connection can read UPDATED yet be hours old, and this pulls fresh data WITHOUT disconnecting/reconnecting. Pass items as an array of selectors (item_id, connector_id, connector_name, or the user-set custom_label nickname); OMIT items to sync ALL linked banks. Returns { results, errors }; each result has the final status, executionStatus, lastUpdatedAt (advances when data is refreshed), and synced (true = fresh data is ready). needs_action (e.g. MFA_REINTERACTION / LOGIN_ERROR / WAITING_USER_INPUT) means the user must re-authenticate — those results include a reconnect_url that opens the widget in UPDATE mode for that exact connection (user enters credentials / MFA token, data refreshes in place, no slot consumed, no disconnect needed). timed_out: true means the sync is still running — re-check with openfinance_get_item_status. Set wait: false for fire-and-forget (returns immediately while UPDATING).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
waitNo
itemsNo

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. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already indicate mutation (readOnlyHint=false). Description adds details: waits up to ~60s, polls until item stops updating, returns reconnect_url for MFA scenarios, and confirms no disconnect/reconnect needed.

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 dense paragraph that effectively front-loads key action. Could be improved with structure (e.g., bullet points), but no waste and covers all necessary details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Comprehensive for 2-param tool without output schema. Details return structure (results, errors), status fields, timed_out handling, and MFA reconnection flow. References sibling tool for continued polling.

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

Parameters5/5

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

Schema coverage 0%, but description compensates fully: explains wait as boolean for sync mode, items as array of selectors (item_id, connector_id, etc.), and omitting syncs all linked banks.

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 'forces bank to re-sync connections' with specific verb-resource. Distinguishes from sibling openfinance_get_item_status by explaining that it pulls fresh data without disconnect/reconnect.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use (stale balance/transaction list) and provides usage variants: omit items to sync all, set wait=false for fire-and-forget. References sibling tool for polling on timeout.

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

All Monte Bravo 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 target distinct resource/action pairs, but openfinance_list_connections and openfinance_get_item_status overlap on connection status/reconnect URLs, and openfinance_list_transactions vs openfinance_list_transactions_by_item can be confused. The long descriptions reduce ambiguity, but selection risk remains.

Naming Consistency3/5

The openfinance_* block is consistently verb_noun, but the platform tools mix bare verbs (authenticate, connect), nouns (marketplace), and noun_info (toolkit_info). No single naming convention spans the whole set, though each subgroup is internally readable.

Tool Count3/5

At 25 tools, this sits at the top of the heavy borderline range. The broad scope—MCP.AI platform management, prompt library, and Open Finance data—justifies many tools, but the set feels like a bundled suite rather than a tightly scoped single-purpose server.

Completeness4/5

The Open Finance side is well covered: accounts, balances, transactions, credit card bills, loans, investments, connections, sync, status, provider health, and category updates. The platform side has auth, toolkit info, marketplace, and feedback. Minor gaps exist, such as no explicit identity fetch or payment initiation, but those seem outside the intended read/analysis domain.

Resources