Conta Azul MCP

contaazul_list_sales

Read-onlyIdempotent

Lista vendas (GET /venda/busca). Filtros: data_inicio/data_fim (emissão, AAAA-MM-DD), data_criacao_de/ate (AAAA-MM-DD), data_alteracao_de/ate (AAAA-MM-DDTHH:MM:SS), ids_clientes, ids_vendedores, ids_categorias, ids_produtos, numeros, situacoes (ex.: aprovado, em_andamento, faturado, cancelado, orcamento), termo_busca, ordenação por numero/cliente/data. Paginação: pagina + tamanho_pagina; a resposta traz total_itens, totais e quantidades por situação.

Bulk support: accepts cliente_ids for batched execution.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tipos`	No
`pagina`	No
`totais`	No
`account`	No
`numeros`	No
`origens`	No
`data_fim`	No
`situacoes`	No
`cliente_id`	No
`cliente_ids`	No
`data_inicio`	No
`termo_busca`	No
`ids_clientes`	No
`ids_produtos`	No
`status_venda`	No
`ids_categorias`	No
`ids_vendedores`	No
`tamanho_pagina`	No
`data_criacao_de`	No
`data_criacao_ate`	No
`data_alteracao_de`	No
`data_alteracao_ate`	No
`campo_ordenado_ascendente`	No
`campo_ordenado_descendente`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedOct 2, 2026

addedInput schema / properties / campo_ordenado_ascendente

Added value: +{
+  "enum": [
+    "numero",
+    "cliente",
+    "data"
+  ],
+  "type": "string"
+}

addedInput schema / properties / campo_ordenado_descendente

Added value: +{
+  "enum": [
+    "numero",
+    "cliente",
+    "data"
+  ],
+  "type": "string"
+}

addedInput schema / properties / data_alteracao_ate
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / data_alteracao_de
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / data_criacao_ate
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / data_criacao_de
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / ids_categorias

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / ids_clientes

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / ids_produtos

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / ids_vendedores

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / numeros

Added value: +{
+  "items": {
+    "type": "number"
+  },
+  "type": "array"
+}

addedInput schema / properties / origens

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / situacoes

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / termo_busca
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / tipos

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / totais

Added value: +{
+  "enum": [
+    "waiting_approved",
+    "approved",
+    "canceled",
+    "all"
+  ],
+  "type": "string"
+}

Changed8 schema fields changedJun 5, 2026
- 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."
```
- removedInput schema / properties / cliente_ids / description
```
Removed value: -"Bulk mode: multiple values for cliente_id"
```
- removedInput schema / properties / pagina / maximum
```
Removed value: -9007199254740991
```
- removedInput schema / properties / pagina / minimum
```
Removed value: -1
```
- changedInput schema / properties / pagina / type
```
Previous value: -"integer"New value: +"number"
```
- removedInput schema / properties / tamanho_pagina / maximum
```
Removed value: -100
```
- removedInput schema / properties / tamanho_pagina / minimum
```
Removed value: -1
```
- changedInput schema / properties / tamanho_pagina / type
```
Previous value: -"integer"New value: +"number"
```
First observedMay 29, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuinely useful behavior beyond that: pagination mechanics (pagina + tamanho_pagina), the shape of the response (total_itens, totais, quantidades por situação), and a bulk-execution mode via cliente_ids.

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?

Front-loads the verb, resource and endpoint, then groups filters compactly; the appended bulk-support note is somewhat detached but short. The density is justified by 24 undocumented parameters, though the run-on filter sentence is slightly hard to parse.

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?

No output schema exists, so the description usefully summarizes return fields and pagination, and it adds bulk-mode behavior. Given 24 parameters at 0% schema coverage, a few parameters remain undocumented in any field, leaving minor gaps for an agent constructing complex queries.

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?

With 0% schema description coverage the description must carry the load, and it documents most filters, including the non-obvious date formats (AAAA-MM-DD vs AAAA-MM-DDTHH:MM:SS) and the ordering dimension. It still omits several declared parameters (tipos, totais, account, origens, status_venda, cliente_id), so it does not fully compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ("Lista vendas") and even maps it to the backend endpoint (GET /venda/busca), so an agent knows exactly what the tool retrieves. It does not explicitly differentiate itself from the sibling get_sale or list_sale_items, which the 5-level asks for, but the scope is otherwise unambiguous.

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?

Usage is only implied: the enumeration of filters and the pagination parameters signal this is the filtered bulk-listing endpoint, but there is no explicit when-to-use or when-to-prefer-an-alternative (e.g., use get_sale for a single sale). No exclusions or prerequisites are given.

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 tools Inspect

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.

contaazul_list_sales

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources