Skip to main content
Glama

PagBank MCP

by io.github.mcp-dir

openfinance_list_connections

Read-onlyIdempotent

Returns the saved bank connections for this install: connector_id, item_id, bank name, a per-connection reconnect_url, and an add_connection_url to link additional banks via the Open Finance widget. The reconnect_url reopens the widget in UPDATE mode for that EXISTING connection (user re-enters credentials / MFA token and the data refreshes in place) — use it when a connection needs re-authentication (MFA connectors, LOGIN_ERROR, stale non-Open-Finance data). It does NOT consume a connection slot and does NOT require disconnecting first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds useful behavioral details about reconnect_url (reopens widget in UPDATE mode) and add_connection_url, but does not contradict annotations.

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?

Description is slightly long but each sentence provides valuable information. It is front-loaded with the main return values and clearly explains the purpose of special URLs.

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?

For a list tool with no output schema, the description fully explains what is returned (fields and URLs) and the behavior of reconnect_url and add_connection_url. No gaps remain.

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

Parameters4/5

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

No parameters exist (schema coverage 100% with empty schema). Baseline 4 per rule for 0 parameters; description does not need to add parameter information.

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 it returns saved bank connections with specific fields (connector_id, item_id, bank name, reconnect_url, add_connection_url). It distinguishes itself from sibling tools like openfinance_disconnect_bank and openfinance_force_sync by focusing on listing connections and providing URLs for reconnection and adding new connections.

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 provides explicit guidance on when to use the reconnect_url (for connections needing re-authentication due to MFA, LOGIN_ERROR, or stale non-Open-Finance data). It also clarifies that reconnect_url does not consume a connection slot and does not require disconnecting first, helping the agent decide between this tool and others.

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