Skip to main content
Glama
JoaoLucasAl

mcp-server-efi

by JoaoLucasAl

Devolver parcela Pix recorrente do Open Finance

of_devolution_recurrency_pix
Destructive

Refund a payment in an Open Finance recurring PIX after identifying the installment and confirming the amount.

Instructions

Solicita a devolução de um pagamento executado dentro de uma recorrência Open Finance. Use após identificar a parcela e conferir o valor, pois há movimentação de recursos.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesDados enviados no corpo da operação.
paramsYesParâmetros de rota ou consulta exigidos pela 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 Devolver parcela Pix recorrente do Open Finance.
idempotency_keyYesChave opcional de idempotência. Quando omitida, o servidor gera uma chave para esta chamada.
Behavior4/5

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

The description adds context beyond annotations by warning 'pois há movimentação de recursos', which aligns with the destructiveHint: true annotation. No contradictions, but could disclose more about reversibility or auth needs.

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: first states purpose, second gives usage guidance. No extraneous words, front-loaded with key information.

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?

Given the output schema exists and the tool is part of a complex recurrency system, the description is adequate but could include more detail on prerequisites or effects. Nevertheless, it is sufficient for an agent.

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 coverage is 100% and each parameter has a description. The description does not add additional meaning beyond what the schema provides.

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 verb 'Solicita a devolução' and the resource 'pagamento executado dentro de uma recorrência Open Finance'. It distinguishes from siblings like 'of_devolution_pix' by specifying it's for a recurrency payment.

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 when to use: 'após identificar a parcela e conferir o valor' and warns about fund movement. It provides clear context but does not explicitly mention alternatives or when not to use.

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