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 and idempotentHint, covering safety. The description adds behavioral detail about the response shape in different states. However, it does not describe partial connectivity scenarios, leaving a small gap.
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, then conditional details. No wasted words, and the structure is easy to scan.
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 no-parameter status tool with rich annotations, the description covers the main use cases well. It explains both fully-connected and missing-credentials states, though it leaves partial connectivity ambiguous.
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 the input schema is empty. The description doesn't need to cover parameter details, and the schema coverage is 100% vacuously. Baseline 4 applies.
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 returns connection status and URLs, with specific detail on two outcomes. This is a distinct verb+resource that differentiates it from siblings like 'authenticate' which initiates connections.
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 provides context on when the tool is useful by describing the two scenarios (all connected vs. missing credentials). It implies the user should call this to check connection state, though it does not explicitly mention alternatives or exclusions.
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.
Most tools are distinct in purpose, but there is some overlap between authenticate, connect, and marketplace—especially since marketplace's invoke can return connection links. The single domain-specific tool (cnpj_cadastral_plus_consultar) is clearly separate from the platform utilities.
Naming is inconsistent: it mixes English and Portuguese, verb-only (authenticate, connect), noun-only (marketplace), and snake_case verb_noun (report_bug, show_version) with no coherent pattern. The Portuguese tool name cnpj_cadastral_plus_consultar follows a different convention entirely.
With 7 tools, the count is reasonable, but only one actually relates to the server's apparent domain (CNPJ data). The remaining six are generic platform utilities (marketplace, connect, toolkit_info, etc.) that don't belong in a specialized server and dilute its focus.
The CNPJ domain is severely underrepresented: there is only a single query tool and no other operations such as validation, list, or update. The generic platform tools do not fill these gaps, making the set incomplete for its stated purpose.