hivecloud_cte_excluir
Destructive
Exclui um ou mais CT-e (rascunhos/rejeitados, por id). Irreversível. Exige allow_writes.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ids | Yes | ||
| account | No | ||
| empresa_id | No |
HiveCloud CT-e / MDF-e
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already flag destructiveHint=true, but the description adds valuable behavioral context: the operation is irreversible and requires the 'allow_writes' flag. This goes beyond the structured data by clarifying permission prerequisites and non-reversibility.
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?
The description is extremely concise, using a single sentence to state the action, scope, irreversibility, and permission requirement. Every word adds value with no fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple delete operation, the description covers the essential context (irreversibility, permission). However, it omits details about response behavior, error conditions, or whether it's a hard delete, which would be useful but not critical given the tool's straightforward nature.
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 coverage is 0% and the description offers no parameter explanations. While parameter names like 'ids' and 'account' are self-explanatory, the description fails to compensate for the lack of schema descriptions, even though the 'por id' phrase hints at 'ids' usage.
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 action ('Exclui' - deletes) and the resource (CT-e), specifying they are drafts/rejected ones selected by ID. This distinguishes it from sibling operations like cancellation, making the purpose unambiguous.
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 provides clear usage context by specifying the tool applies to drafts/rejected CT-e and warns it is irreversible, requiring the 'allow_writes' permission. While it doesn't explicitly compare to siblings like 'hivecloud_cte_cancelar', the scope is well-defined.
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.4/5.0
Disambiguation2/5
The server mixes two distinct domains (HiveCloud fiscal documents and mcp.ai platform controls) with several similarly-named tools (hivecloud_list_ctes vs hivecloud_get_cte vs hivecloud_cte_xml; hivecloud_list_mdfes vs hivecloud_get_mdfe). The generic 'authenticate', 'connect', and 'toolkit_info' overlap in connection/account status purposes, creating ambiguity about which to call for setup.
Naming Consistency3/5
Tools mostly follow a 'hivecloud_<domain>_<action>' pattern (e.g., hivecloud_cte_emitir, hivecloud_cte_cancelar), but there are exceptions like 'hivecloud_avaliar' (short verb without domain), 'get_cte' vs 'list_ctes' (tense/plural inconsistency), and generic tools 'authenticate', 'connect', 'report_bug' that don't follow the pattern. Mixed Portuguese/English verbs further reduce consistency.
Tool Count2/5
With 33 tools, this is on the heavy side. The domain spans CT-e, MDF-e, NF-e, DC-e, plus platform management (marketplace, toolkit, bug reporting, versioning) — it bundles too many concerns into one server. Several tools (report_bug, show_version, marketplace) feel unrelated to HiveCloud fiscal document handling, making the count feel bloated.
Completeness4/5
For the CT-e and MDF-e lifecycle, the surface is quite complete: create from NF-e, emit, cancel, edit (carta de correção), delete drafts, print DACTE/DAMDFE, export XML, list/get, and even a travel report. DC-e and NF-e are lighter (only list/query), and missing tools like 'create_mdfe' (no draft creation for MDF-e) or 'update_mdfe' (only cancel/end) are notable gaps. However, core workflows are well covered.