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?
Goes beyond readOnly annotation by explaining exact responses in two cases, including the presence of 'authenticated' and 'pending' fields, and the return of connect_url when credentials are missing.
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 main purpose, and each sentence provides useful information without 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?
Covers two main scenarios but does not explicitly mention the case where only some providers are connected, which could be a potential gap. However, given the simplicity, it is mostly 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?
No parameters exist in the schema, so the description correctly omits any parameter details; nothing to add.
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?
Clearly states it returns connection status and URLs, with specific details on two scenarios, distinguishing it from sibling tools like authenticate or toolkit_info.
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?
Provides context on when to use by describing the behavior in two situations: when all providers are connected and when credentials are missing, implying it's for checking connection status and obtaining connect URLs.
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 have distinct purposes, but 'authenticate' and 'connect' both involve authentication flows, and 'toolkit_info' overlaps slightly with 'connect' regarding status. The descriptions are detailed enough to differentiate them, but the boundary between these administrative tools could lead to some mis-selection.
Names use consistent snake_case, but conventions vary: some are verbs (authenticate, connect, report_bug, show_version) while others are nouns (marketplace, toolkit_info). The domain-specific 'cade_processos_consultar' breaks the pattern by mixing a proper noun with a verb. Overall, the mixture is readable but not uniform.
Seven tools is within the ideal range and each earns its place for platform management. However, the server is titled 'CADE: Processos' yet only one tool is domain-specific, making the count feel imbalanced. A slightly smaller number of utility tools would better match the apparent purpose.
The server offers only a single domain operation ('cade_processos_consultar') for what appears to be a legal processes server. There are no list, get-details, or workflow operations beyond the one query, leaving significant gaps for common use cases. The rest of the tools are unrelated to the domain, focused on platform administration.