Skip to main content
Glama

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

TDQS

A4.9/5.0
Behavior5/5

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

The description discloses many behavioral traits beyond annotations: it is a write operation that waits up to 60s, can require re-authentication, returns specific fields, and can time out. This is comprehensive, and no contradiction with annotations is present.

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 detailed but front-loaded with the core action. Every sentence adds value, though it is slightly long. It could be tightened, but remains efficient for the complexity.

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?

Given no output schema, the description thoroughly explains the return structure, including error conditions and handling. It covers all necessary context for successful use, making it complete.

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?

The description adds significant meaning to the parameters: 'wait' is explained as fire-and-forget option, and 'items' is described as an array of selectors (item_id, connector_id, etc.) and that omitting it syncs all banks. This compensates for zero schema description coverage.

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 the tool forces a bank to re-sync connections and waits for completion. It specifies the verb 'force_sync', the resource 'bank connections', and distinguishes it from other tools by mentioning it does not 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?

The description explicitly says when to use it (when balance/transaction list looks stale) and what it does without disconnecting. It also explains options like 'wait: false' for fire-and-forget and how to handle errors like 'needs_action' or 'timed_out', providing clear guidance.

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

All Porto Bank 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
Disambiguation5/5

Each tool targets a distinct resource and action: balances, transactions, bills, loans, investments, connections, categories, and system functions. While some tools are related (e.g., list_transactions vs list_transactions_by_item), their purposes are clearly separated by granularity and intent, with no true overlap.

Naming Consistency5/5

The Open Finance tools follow a strict 'openfinance_verb_noun' pattern (e.g., list_accounts, get_balance, update_transaction_category), and the broader system tools use clear verb-based names. All use snake_case consistently with no mixing of conventions.

Tool Count4/5

At 25 tools, this is on the higher end of the range, but the breadth is justified by the Open Finance domain: accounts, transactions, bills, loans, investments, connections, plus marketplace and system operations. Each tool adds unique value, though the count is slightly heavy.

Completeness4/5

The server covers the core Open Finance lifecycle: connection management, account/transaction/bill/loan/investment retrieval, category correction, and provider status. Minor gaps like a dedicated 'get single investment' tool are covered by list_investments plus list_investment_transactions. Overall, no dead ends for data access.

Resources