Skip to main content
Glama

PagBank 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

TDQS

A5/5.0
Behavior5/5

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

Adds behavioral details beyond annotations: waits up to 60s, polls, handles errors with reconnect_url, timed_out flag, and no disconnect needed.

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?

Well-structured and each sentence adds value; no unnecessary fluff while covering purpose, parameters, return values, and edge cases.

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?

Complete given complexity: covers sync behavior, polling, error states, return format, and fire-and-forget option.

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 is 0%, but description fully explains both parameters: wait (fire-and-forget) and items (selectors or omit for all).

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 re-sync, waits for completion, and distinguishes it from sibling tools like openfinance_get_item_status.

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 balances/transactions), provides alternative actions (re-check with get_item_status), and explains fire-and-forget mode via wait:false.

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

All PagBank 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 openfinance_* tool targets a distinct resource (account, transaction, bill, loan, investment) with a clear action (get/list/update/force_sync). The administrative tools (connect, authenticate, report_bug) are clearly separate. No two tools appear to perform the same function.

Naming Consistency4/5

The openfinance_* tools follow a consistent verb_noun pattern (e.g., get_account_balance, list_transactions, update_transaction_category). Minor deviations like openfinance_provider_status (lacks a verb) and openfinance_force_sync (verb phrase) slightly break the pattern, but the overall convention is predictable.

Tool Count4/5

25 tools is on the higher end but appropriate for a comprehensive Open Finance server covering accounts, transactions, bills, loans, investments, connections, and administration. Each tool has a distinct purpose and none feel redundant.

Completeness5/5

The tool surface is complete for the domain: it covers connection management (connect/disconnect/force sync/status), account and transaction queries, credit card bills, loans, investments, and transaction categorization, plus admin utilities. No obvious gaps that would block typical workflows.

Resources