contaazul_contract_write
Cria um contrato. data é o payload em JSON.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | ||
| account | No |
Conta Azul MCP
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Changed1 schema field changed
- removed
Input schema / properties / account / descriptionRemoved value: -"Quando o install tem mais de uma empresa Conta Azul: company_id, label, ou parcial. Ver contaazul_list_accounts."
- First observed
TDQS
C2.7/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=false, but the description only repeats that it creates a contract. No additional behavioral traits are disclosed, such as side effects, required permissions, or idempotency.
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?
The description is concise with two sentences. It front-loads the purpose and adds a brief param hint. However, it could be better structured with separate sections for usage or parameters.
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 (2 params, no output schema), the description is incomplete. It lacks guidance on the payload structure, error handling, response format, and the account parameter's role.
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?
Schema description coverage is 0%, so the description must provide meaning. It adds that 'data' is a JSON payload, but does not explain its structure or the optional 'account' parameter. This is minimal extra value.
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 clearly states 'Cria um contrato' (Creates a contract), specifying the verb and resource. It distinguishes from sibling tools like get, list, delete, and terminate contracts, but does not differentiate from other write tools like contaazul_sale_write_create.
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 is no mention of prerequisites, context, or situations where this tool should be avoided.
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
C2.9/5.0
Disambiguation2/5
Multiple tools are easily confused: person_write_create/person_write_update and sale_write_create/sale_write_update duplicate the same operation with an internal action flag, and authenticate vs connect both deal with connection setup. Also, list_accounts (company installs) and list_financial_accounts (bank accounts) have similar names but different meanings.
Naming Consistency2/5
Naming patterns vary widely: verb_noun (create_budget, list_people) is mixed with noun_verb (contract_write, person_delete, product_write). The contaazul_ prefix is applied inconsistently, and standalone names like authenticate, connect, marketplace, and toolkit_info break the pattern. Flattened action pairs add redundant, non-idiomatic names.
Tool Count1/5
With 57 tools, this server exceeds the 50+ threshold for an extreme count. The tool list is bloated with generic platform tools (authenticate, marketplace, report_bug) alongside dozens of domain-specific ones, making it overwhelming for agents to parse and select from.
Completeness4/5
The Conta Azul domain is well represented: people, products, services, sales, budgets, contracts, financial accounts, receivables/payables, settlements, charges, invoices, and transfers all have read/create/list operations, and most have update/cancel/delete. Minor gaps like product update/delete or service update exist due to API limitations, but the core workflows are covered.