Skip to main content
Glama
Sign In

Conta Azul MCP

by io.github.douglac
OverviewDiscussionsAdmin

contaazul_payable_create

Cria um evento financeiro de conta a pagar. data é o JSON do EventoFinanceiroRequest. OBRIGATÓRIOS (a chamada é recusada antes de ir à API se faltar algum): id_fornecedor (UUID do fornecedor, via contaazul_list_people; contato é aceito como alias), conta_financeira (UUID, via contaazul_list_financial_accounts), data_competencia (YYYY-MM-DD), descricao, valor (number > 0), rateio[] com {id_categoria (UUID, via contaazul_list_categories), valor} (um id_categoria na raiz vira rateio de 100%) e condicao_pagamento.parcelas[] (cada: data_vencimento YYYY-MM-DD e detalhe_valor:{valor_bruto obrigatório; valor_liquido derivado se omitido}; descricao e conta_financeira da parcela, se omitidas, herdam as do lançamento; os aliases valor_composicao e composicao_valor são normalizados automaticamente). metodo_pagamento da parcela usa o enum EXATO da API (PIX_PAGAMENTO_INSTANTANEO, BOLETO_BANCARIO, TRANSFERENCIA_BANCARIA, CARTAO_CREDITO, CARTAO_DEBITO, DINHEIRO etc — formas curtas como PIX/BOLETO/TED são normalizadas). Retorna 202 + {protocolId,status} (assíncrono).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "data": "<data>"
    },
    "name": "contaazul_payable_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYes
accountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / account / description
      Removed value: -"Quando o install tem mais de uma empresa Conta Azul: company_id, label, ou parcial. Ver contaazul_list_accounts."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare the write/non-idempotent/non-destructive profile, and the description adds substantial context beyond them: client-side validation before hitting the API, asynchronous 202 with protocolId/status, automatic alias normalization (contato, valor_composicao, PIX/TED short forms), and inheritance rules for parcela fields. These are the exact behaviors an agent cannot infer from the annotations.

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?

Purpose is front-loaded and every clause carries required-field or normalization information, so little is wasted. The structure is a single dense paragraph with deeply nested parentheses, which hurts scanability for a spec this long.

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 a complex nested JSON payload, no output schema, and no param documentation, the description is unusually complete: it covers required fields, derivation rules, aliases, and the async return shape. Only the 'account' parameter and any error-response behavior remain undocumented.

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

Parameters4/5

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

Schema coverage is 0% and the schema only types 'data' as a bare string, so the description carries the full burden — it enumerates the required EventoFinanceiroRequest keys, formats (YYYY-MM-DD, valor > 0), the rateio[] and parcelas[] sub-structures, and accepted aliases. The second parameter 'account' is left completely unexplained in both schema and description, which is the one real gap.

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?

States a specific verb and resource ('Cria um evento financeiro de conta a pagar') and makes the payable-vs-receivable distinction clear against the sibling contaazul_receivable_create. The async 202 + {protocolId,status} return note further pins down what the call does.

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?

Explicitly names the prerequisite lookups for every foreign key (id_fornecedor via contaazul_list_people, conta_financeira via contaazul_list_financial_accounts, id_categoria via contaazul_list_categories) and warns that the call is rejected pre-API if any required field is missing. It does not state when to prefer a different tool (e.g. receivable_create or an update path), so no exclusions are offered.

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

All Conta Azul MCP 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