Caixa Postal e-CAC
caixa_postal_ecacRead-only
Consulta mensagens da Caixa Postal do e-CAC classificadas por prioridade e tipo.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| empresaId | No | ID da empresa |
Contazz AutoPilot
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.6/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint=true, and the description's 'Consulta' aligns with this safe read behavior. The addition that messages are classified by priority and type adds some context beyond annotations, but it does not disclose authentication needs, pagination, or response format, so it is adequate but not rich.
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?
A single, front-loaded sentence that directly states the tool's purpose with no redundancy. It is appropriately concise for a simple read operation.
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?
For a read-only tool with one optional parameter and no output schema, the description provides sufficient context about what the tool does. It mentions the content (messages) and classification, though it does not detail return fields. However, given the low complexity, this is nearly complete.
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?
The schema covers the single parameter empresaId with a description ('ID da empresa') at 100% coverage. The tool description adds no parameter-specific meaning, so the schema already carries the full burden.
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 uses a specific verb 'Consulta' (query) and identifies the resource 'Caixa Postal do e-CAC' (e-CAC mailbox), adding that messages are classified by priority and type. This clearly distinguishes it from sibling tools like procuracoes_ecac, which deals with powers of attorney.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. There are no explicit exclusions, prerequisites, or reference to sibling tools, leaving the agent to infer usage solely from the description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
B3.1/5.0
Disambiguation3/5
Many tools have distinct purposes, but several overlap: 'calcular_cbs_ibs' and 'consultar_aliquota_cbs_ibs' both deal with CBS/IBS rates, 'criar_cobranca' and 'criar_cobranca_pix' create similar things, and multiple metrics tools (dashboard_executivo, saude_financeira, autopilot_regua) could confuse an agent. The reconciliation_* group is well-differentiated, but overall the large, overlapping surface creates ambiguity.
Naming Consistency2/5
Names mix Portuguese and English inconsistently (e.g., 'agendar_cobranca' vs. 'subscribe_webhook'). Most Portuguese names follow verb_noun, but many English names are noun_verb (e.g., 'reconciliation_execute') rather than verb_noun. Additionally, some names are vague or non-descriptive ('autopilot_regua', 'badges_contadores', 'metricas_escritorio'), breaking any predictable pattern.
Tool Count2/5
61 tools is excessive for most MCP servers, even for a broad financial/fiscal automation domain. The count feels bloated, and several tools (e.g., criar_orcamento, listar_orcamentos) are dead weight being deactivated. This would likely be better split into multiple focused servers (e.g., cobranças, reconciliation, fiscal).
Completeness3/5
The tool surface covers many workflows: cobranças, NFS-e, reconciliation, tax simulation, dashboards, webhooks, and client insights. However, there are notable gaps in basic CRUD: no update/delete for cobranças or clientes, and no way to manage orcamentos (they're deactivated). The reconciliation module is very complete, but the overall surface has dead ends and missing lifecycle operations.