Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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, idempotentHint, and non-destructive behavior. The description adds valuable context beyond annotations: it discloses the two possible output states (connected vs. missing credentials) and what fields are returned in each case.
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?
Two sentences, front-loaded with the core purpose, and every clause adds meaningful information about the tool's behavior. No wasted words.
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 zero-parameter status check with strong annotations, the description covers both the happy path and the missing-credentials state adequately. It does not fully specify the exact shape of the 'pending' field or URL properties, but no output schema exists and the description provides enough for an agent to invoke and interpret results.
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 tool has zero parameters and schema coverage is trivially 100%. Per the rubric, a zero-parameter tool gets a baseline of 4, and the description appropriately does not need to explain parameter semantics.
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 uses a specific verb ('Returns') and resource ('connection status and URLs'), clearly stating what the tool does. It also distinguishes itself from sibling tools by focusing on status rather than performing authentication actions.
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 implies usage as a connection status check by describing the conditional outputs, but it does not explicitly state when to use this tool versus alternatives like 'authenticate'. No exclusions or alternative recommendations are provided.
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.