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 about return values in two different scenarios, which goes beyond the annotations. 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?
Two sentences, front-loaded with the primary purpose, no unnecessary words. Very concise and well structured.
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?
With no output schema, the description carries the burden of explaining return values. It covers the all-connected and missing-credentials cases but omits partial-connection states. Still, given the tool's simplicity and good annotations, it is fairly complete.
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 schema description coverage is 100% by default. The baseline for 0 params is 4; the description appropriately does not need to add parameter-level detail.
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?
Description clearly states it returns connection status and URLs, with a specific verb and resource. It distinguishes itself from sibling tools like 'authenticate' by focusing on status rather than performing authentication.
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?
Description provides behavioral conditions (all connected vs missing credentials) but lacks explicit guidance on when to use this tool over alternatives like 'authenticate'. Usage context is implied but no exclusions or alternatives are named.
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.
Each tool has a clearly distinct purpose: authenticate handles login, connect checks connection status, ibama_embargos_consultar is the only domain operation, and the rest are platform utilities. No two tools overlap in function.
Naming styles are mixed: single verbs (authenticate, connect), a Portuguese snake_case domain tool (ibama_embargos_consultar), and English verb_noun combinations (report_bug, show_version, toolkit_info). This inconsistency makes the set feel disjointed.
The count of 7 is within a reasonable range, but the server named 'IBAMA Embargos' carries only one domain tool while the other six are generic platform utilities. This composition dilutes the server's focus and makes the count feel disproportionate to its stated purpose.
The domain surface is severely limited: only a single consult operation for embargo certificates. There are no other domain-relevant actions, and the platform tools are unrelated to the core domain, leaving obvious gaps for any workflow beyond a simple query.