Skip to main content
Glama

PicPay 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 are not contradictory. The description reveals polling behavior (~60s timeout), mutation (PATCH), return structures (status, executionStatus, synced), and reauthentication handling (needs_action with reconnect_url). It adds significant context beyond readOnlyHint=false and destructiveHint=false.

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 well-structured: main action, use case, parameter details, return fields, edge cases. It is slightly long but every sentence adds value. Could be tightened slightly but still effective.

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 fully explains input parameters and return fields (results, errors, status, executionStatus, lastUpdatedAt, synced, needs_action, reconnect_url, timed_out). It covers error handling, timeout, and fallback. Complete for a tool of this complexity.

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%, so description must carry the burden. It thoroughly explains the `items` parameter (array of selectors like item_id, connector_name, custom_label) and the `wait` parameter (default behavior and fire-and-forget). Adds meaning that the schema alone does not convey.

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 and waits for completion. It distinguishes from siblings like openfinance_get_item_status by framing it as a refresh tool and noting the alternative check. The verb 'forces' and resource 'connections' are specific, and the scope (one or all) is explicit.

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 states when to use (stale balance/transactions) and what not to do (no disconnect/reconnect). Provides alternatives like openfinance_get_item_status for timed_out cases. Describes optional fire-and-forget behavior with wait: false, giving clear use-case guidance.

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

All PicPay 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
Disambiguation4/5

Most tools have clearly distinct purposes, especially within the openfinance_* family where each targets a different resource or action. A few minor overlaps exist—connect vs toolkit_info both report connection state, and marketplace internally includes report_bug while a top-level report_bug also exists—but these are unlikely to cause serious misselection.

Naming Consistency4/5

The openfinance_* tools follow a consistent snake_case prefix with mostly verb_noun patterns like list_accounts, get_item_status, and force_sync. The general tools are also snake_case but mix verbs (connect, authenticate) with nouns (marketplace, toolkit_info), and openfinance_provider_status breaks the verb_noun pattern slightly.

Tool Count3/5

25 tools is at the upper boundary of a heavy surface, but the Open Finance domain genuinely spans connections, accounts, transactions, bills, loans, investments, categories, and provider health. It feels dense rather than bloated, though a few general utilities like show_version and report_bug could arguably be consolidated.

Completeness4/5

The Open Finance surface is well covered: connection management, account/balance/transaction retrieval, credit card bills, loans, investments, category correction, force sync, and provider status are all present. Minor gaps exist—such as no direct investment position detail endpoint beyond the portfolio list, and payments/initiation are out of scope—but agents can accomplish the core read-only financial workflows without dead ends.

Resources