PagSeguro

pagseguro_charges_refund

Cobranças (charges) no PagSeguro. Ações:

get: detalhe de UMA cobrança (requer charge_id).
cancel: cancela uma cobrança ainda não capturada (charge_id).
refund: estorna uma cobrança (charge_id; amount_cents opcional = estorno parcial).

[Flattened action: refund]

Bulk support: accepts charge_ids for batched execution.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "charge_id": "<charge_id>"
    },
    "name": "pagseguro_charges_refund"
  }
}

Input Schema

Name	Required	Description	Default
`account`	No
`charge_id`	Yes
`charge_ids`	No
`amount_cents`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 11, 2026

TDQS

C2.5/5.0

Behavior2/5

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

The description lists actions that may not all be available (get, cancel) and does not disclose side effects, prerequisites, or error conditions. Annotations provide minimal safety info but description adds confusion rather than clarity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is moderately concise but includes extraneous information about get and cancel actions that are not core to the refund tool. The bullet list helps structure but could be more focused.

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

Completeness2/5

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

The description covers refund and bulk support but lacks details on return values, error handling, prerequisites (e.g., charge status), and does not mention the account parameter. Insufficient for a 4-parameter tool with no output schema.

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

Parameters3/5

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

The description explains charge_id as required, amount_cents as optional for partial refund, and charge_ids for bulk. However, the account parameter is not explained, and with 0% schema coverage, more detail is needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description lists multiple actions (get, cancel, refund) but the tool name and 'Flattened action: refund' indicate it is for refund. This ambiguity dilutes clarity; the purpose is not singularly clear.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus sibling tools like pagseguro_charges_cancel or pagseguro_charges_get. The description does not compare or contrast with alternatives.

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

All PagSeguro tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.