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 read-only, idempotent, and non-destructive behavior. The description adds valuable context on response states ('authenticated:true', 'pending[]' empty) and URL fields under different credential conditions. This goes beyond the structured annotations to inform the agent about expected outcomes.
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 sentences, front-loaded with the core purpose, and every sentence adds useful information. No redundancy or filler.
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?
Given the simplicity (no parameters, no output schema), the description covers the main return scenarios and key fields. However, it does not explicitly address partial connectivity states beyond 'all connected' and 'credentials missing', which leaves a small gap in completeness. Still, it is sufficient for most use cases.
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, so the schema is fully covered (100%). The description correctly does not add parameter details since none exist, and the baseline for zero-parameter tools is 4.
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 clearly states the tool's function with a specific verb ('Returns') and resource ('connection status and URLs'), immediately distinguishing it from the sibling 'authenticate' tool. It also provides concrete output examples under different conditions, leaving no ambiguity about the tool's role.
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 usage is implied: you use this tool to check connection status or retrieve URLs for authentication. However, it does not explicitly state when to use this tool versus alternatives like 'authenticate' or when not to use it. The description offers clear context about behavior but lacks direct guidance on tool selection.
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.
There is a separate report_bug tool while marketplace also mentions report_bug internally, causing duplication. Additionally, authenticate and connect both deal with authentication/connection status, creating boundary confusion.
Tool names mix English and Portuguese (authenticate vs nfe_completa_consultar), and mix verb forms (authenticate, connect) with noun forms (marketplace, toolkit_info), with no consistent verb_noun pattern.
Seven tools is a reasonable number for a server, but the massive marketplace tool bundles dozens of operations into a single tool, making the set feel both overcrowded and under-represented.
The NFe consultation itself is a single query tool, and the rest are platform utilities not directly related to NFe, so the domain coverage is thin. Missing functions like listing past consultations or managing account credits, though the core consult works.