Skip to main content
Glama
Sign In

Pagar.me

by io.github.mcp-dir
OverviewDiscussionsAdmin

pagarme_charges_cancel

Destructive

Cancela/estorna uma cobrança no Pagar.me V5 (requer charge_id; data opcional com amount p/ estorno parcial). Irreversível.

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": "pagarme_charges_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataNo
accountNo
charge_idYes
charge_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate destructiveHint=true. Description adds 'Irreversível' (irreversible) which is critical behavioral context. Does not detail other behaviors like auth needs or rate limits, but the added context is valuable.

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?

Two sentences with no waste. First sentence front-loads main purpose and key params. Second sentence adds bulk support. Efficient and well-structured.

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

Completeness4/5

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

For a medium-complexity tool with 4 params and no output schema, the description covers the main operation, partial refund, and bulk. No mention of error handling or prerequisites, but annotations provide additional context.

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?

With 0% schema description coverage, the description compensates well: explains charge_id as required, data as optional with amount for partial refund, and charge_ids for bulk. Only 'account' parameter is left unexplained, giving ~75% 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 cancels/refunds a charge on Pagar.me V5, specifies required charge_id and optional data with amount for partial refund. It distinguishes from sibling tools like capture or confirm by focusing on cancellation/refund.

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

Usage Guidelines4/5

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

Provides explicit usage context: requires charge_id, optional data for partial refund, and bulk support via charge_ids. Does not explicitly state when not to use or provide alternatives, but context is clear enough for an agent to infer appropriate use.

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

All Pagar.me toolsInspect
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.

Resources