Skip to main content
Glama

Pagar.me

by io.github.mcp-dir
OverviewAdmin

pagarme_customers_write_create

Criar/atualizar clientes e endereços no Pagar.me V5 (só sk_). Ações:

  • create: cria cliente (data: name, email, document, type, …).

  • update: atualiza cliente (requer customer_id; data).

  • create_address: cria endereço (requer customer_id; data).

  • update_address: atualiza endereço (requer customer_id + address_id; data).

  • delete_address: remove endereço (requer customer_id + address_id).

[Flattened action: create]

Bulk support: accepts customer_ids, address_ids for batched execution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
accountNo
address_idNo
address_idsNo
customer_idNo
customer_idsNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

C2.2/5.0
Behavior2/5

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

Annotations indicate destructiveHint=false, but the description includes a delete action. This contradiction is confusing. No details on permissions, rate limits, or side effects.

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 somewhat organized but includes redundant action listings and unclear flattening. It could be more concise without losing information.

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?

Given no output schema and missing parameter explanations, the description is insufficient for reliable use. No details on return values, error handling, or required ID relationships.

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

Parameters1/5

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

Schema coverage is 0% and the description does not explain any parameter semantics. For example, 'data' is a string but its format (JSON?) is unspecified; 'account', 'address_ids', 'customer_ids' have no explanation.

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 it creates/updates customers and addresses, but the mention of multiple actions followed by '[Flattened action: create]' creates ambiguity. It does not clearly distinguish from sibling tools like 'pagarme_customers_write_create_address'.

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 the many sibling tools for similar operations. No exclusions or prerequisites are stated.

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
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.

Resources