Lista os veículos cadastrados (placa, motorista, reboque, tara), usados no MDF-e, paginado. Exige mdfe_tenant_id na conexão.
Bulk support: accepts empresa_ids for batched execution.
| Name | Required | Description | Default |
|---|---|---|---|
| account | No | ||
| pageSize | No | ||
| empresa_id | No | ||
| pageNumber | No | ||
| empresa_ids | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful behavioral context beyond that: pagination, the mdfe_tenant_id connection requirement, and bulk execution via empresa_ids. No contradiction exists.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two short paragraphs with the core purpose and output fields front-loaded. Every sentence adds value: pagination, tenant requirement, and bulk support. There is no filler or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple list tool, the description covers the resource, key returned fields, pagination, the connection requirement, and bulk support. Since there is no output schema, it does briefly indicate return contents, though it omits pagination response details, defaults, or limits. Overall it is adequate for tool selection and invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 0% property descriptions, so the description must compensate. It adds pagination semantics (pageSize/pageNumber) and explains that empresa_ids enables batch execution. However, it does not clarify account, empresa_id, or how singular and plural empresa parameters relate, leaving some parameter ambiguity.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a specific verb ('Lista') and clearly identifies the resource: registered vehicles ('veículos cadastrados') used in MDF-e, including key fields (placa, motorista, reboque, tara). This clearly distinguishes it from sibling list tools like hivecloud_list_motoristas or hivecloud_list_empresas.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description states the tool is for listing vehicles used in MDF-e, that it is paginated, and that it requires mdfe_tenant_id on the connection. It does not explicitly list alternatives or exclusions, but the context is sufficient for choosing this tool among the sibling list tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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.