Skip to main content
Glama
ZuckPay

zuckpay-mcp

Official
by ZuckPay

Criar cobrança PIX

createPixCharge

Create a PIX charge on ZuckPay and receive a copy-paste code, QR code image, and hosted checkout link. Supports idempotency, revenue splits, webhook confirmation, and tracking parameters.

Instructions

Cria uma cobrança PIX na ZuckPay e retorna o código copia-e-cola, a imagem do QR Code e o link de checkout hospedado. Suporta idempotência (external_id_client), split de receita entre contas, webhook de confirmação (urlnoty) e parâmetros de rastreio (UTMs). Valor em reais com até 2 casas decimais.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cpfYesCPF do pagador (11 dígitos; pontuação é removida automaticamente)
fbcNoParâmetro de rastreio fbc (opcional)
fbpNoParâmetro de rastreio fbp (opcional)
sckNoParâmetro de rastreio sck (opcional)
srcNoParâmetro de rastreio src (opcional)
nomeYesNome completo do pagador
emailYesE-mail do pagador
gclidNoParâmetro de rastreio gclid (opcional)
kclidNoParâmetro de rastreio kclid (opcional)
valorYesValor da cobrança em reais (ex: 49.90). Atenção: algumas adquirentes exigem mínimo de R$ 10,00 — a API recusa se for o caso.
fbclidNoParâmetro de rastreio fbclid (opcional)
gbraidNoParâmetro de rastreio gbraid (opcional)
splitsNoDivisão de receita entre contas ZuckPay (2 a 10 recebedores; soma dos percentuais = 100). Calculada sobre o valor líquido.
ttclidNoParâmetro de rastreio ttclid (opcional)
wbraidNoParâmetro de rastreio wbraid (opcional)
urlnotyNoURL https do seu sistema que receberá o postback (webhook) quando o pagamento for confirmado
click_idNoParâmetro de rastreio click_id (opcional)
telefoneYesTelefone do pagador com DDD (ex: 11999998888)
utm_termNoParâmetro de rastreio utm_term (opcional)
descricaoNoDescrição/motivo do pagamento (até 255 caracteres)
product_idNoID de um produto cadastrado na conta ZuckPay (vincula a transação ao produto)
utm_mediumNoParâmetro de rastreio utm_medium (opcional)
utm_sourceNoParâmetro de rastreio utm_source (opcional)
utm_contentNoParâmetro de rastreio utm_content (opcional)
utm_campaignNoParâmetro de rastreio utm_campaign (opcional)
external_id_clientNoID externo do seu sistema (ex: ORDER-123). Garante idempotência: repetir o mesmo ID retorna a mesma cobrança pendente.
Behavior1/5

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

Description claims idempotency support via external_id_client, but annotation 'idempotentHint' is false, creating a contradiction. No other contradictions found, but this is a serious inconsistency.

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 a single, front-loaded sentence that efficiently conveys the tool's purpose and key features. It is concise but could be broken into multiple sentences for better readability.

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

Completeness3/5

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

Given no output schema, the description partially explains what it returns (code, QR, link) but does not detail the response structure or mention required fields. It covers major features but leaves gaps for a complex tool with 26 parameters.

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?

Schema description coverage is 100%, so the schema already documents all parameters. The description adds minimal extra context (e.g., 'Valor em reais com até 2 casas decimais') but does not significantly enhance understanding beyond the schema.

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 states a specific verb (cria) and resource (cobrança PIX), and specifies the outputs (copia-e-cola, QR code, link de checkout). It clearly distinguishes this as the PIX creation tool among siblings like createSpeiCashin and createPayPalOrder.

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 implies usage for PIX payments but does not explicitly say when to use this tool versus alternatives. It lacks guidance on when not to use it or which sibling tools to prefer in specific contexts.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ZuckPay/zuckpay-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server