Skip to main content
Glama
JoaoLucasAl

mcp-server-efi

by JoaoLucasAl

Criar pagamento Pix automático via Open Finance

of_create_automatic_pix_payment
Destructive

Request a PIX payment using a pre-authorized automatic membership. Use after validating membership, receiver, and amount.

Instructions

Solicita um pagamento Pix apoiado por uma adesão automática previamente autorizada. Use após validar adesão, recebedor e valor; a operação pode movimentar recursos.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesDados enviados no corpo da operação.
idempotency_keyNoChave opcional de idempotência. Quando omitida, o servidor gera uma chave para esta chamada.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesValor do campo “result” usado na saída da operação Criar pagamento Pix automático via Open Finance.
idempotency_keyYesChave opcional de idempotência. Quando omitida, o servidor gera uma chave para esta chamada.
Behavior2/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false; the description adds only 'a operação pode movimentar recursos', which repeats the destructive nature without further detail on side effects, authorization, or irreversibility.

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?

The description is a single sentence plus a short instruction, with no wasted words. It effectively communicates the core purpose and precondition in a compact form.

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 the tool's complexity (nested parameters, Open Finance context), the description is too sparse. It omits details about the relationship between parameters, the meaning of 'pagamento' fields, and the flow of the automatic enrollment process. The output schema exists but the description lacks complementary context.

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?

Despite 100% schema coverage, the parameter descriptions are generic and redundant (e.g., 'Valor do campo...'), adding no meaningful semantics beyond the schema. The tool description does not compensate by clarifying the purpose of parameters like 'identificadorAdesao' or 'pagamento'.

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 initiates an automatic Pix payment backed by a pre-authorized enrollment. It specifies the verb 'solicitar' and the resource 'pagamento Pix automático', distinguishing it from other payment tools that require different prerequisites.

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?

The description advises using the tool after validating enrollment, receiver, and amount, and warns that it moves funds. While it does not explicitly list alternatives or when not to use, it provides sufficient context for correct invocation among similar sibling tools.

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/JoaoLucasAl/mcp-server-efi'

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