Skip to main content
Glama
Sign In

Pagar.me

by io.github.mcp-dir
OverviewDiscussionsAdmin

pagarme_transfers_get

Read-onlyIdempotent

Transferências no Pagar.me V5. Ações:

  • list: lista transferências (page, size; data: filtros).

  • get: transferência por transfer_id.

[Flattened action: get]

Bulk support: accepts transfer_ids for batched execution.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pagarme_transfers_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataNo
pageNo
sizeNo
accountNo
transfer_idNo
transfer_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the tool's safety is clear. The description adds that it supports bulk execution, which is useful but does not reveal other behaviors like rate limits or result format.

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 short but includes extraneous list action details that are not relevant to this tool. The flattened action note is helpful but overall structure 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?

No output schema is provided, yet the description does not explain what the tool returns. It also fails to clarify the purpose of ambiguous parameters like page and size, leaving the agent without enough information to use the tool correctly.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must explain parameters. It only explains transfer_id and transfer_ids for bulk, but leaves data, page, size, and account entirely undocumented, leading to potential misuse.

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 states 'get: transferência por transfer_id' which identifies the main purpose, but it also lists a 'list' action that belongs to a sibling tool, causing ambiguity. The '[Flattened action: get]' note helps but is not explicit enough.

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

Usage Guidelines3/5

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

The description indicates the tool is for getting a single transfer and supports batch via transfer_ids, but does not distinguish when to use this tool versus the sibling 'pagarme_transfers_list' for listing. The flattened action note provides some guidance.

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