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 readOnly and idempotent. The description adds meaningful response behavior: it returns authenticated:true with empty pending[] when all providers are connected, and connect_url when credentials are missing. This goes beyond the annotations.
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 result, and contains no redundant or verbose content.
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 zero-parameter read-only tool, the description adequately covers both the success case and the missing-credentials case. No output schema exists, but the returned fields are described enough for an agent to understand the tool's behavior.
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 trivially covers them. A baseline of 4 is appropriate because no parameter explanation is needed.
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. It differentiates from sibling 'authenticate' by focusing on checking status rather than establishing 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?
Usage context is implied: it is the tool to check connection status. However, there are no explicit when-to-use or alternative references, even though sibling tools like 'authenticate' could warrant a comparison.
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 domain tool 'cnd_imovel_rural_consultar' is clearly distinct, but the platform tools overlap: 'connect' and 'toolkit_info' both report connection status, and 'marketplace' is a catch-all for searching, invoking, and managing MCPs. Descriptions are detailed, but the boundaries between these utility tools are not always sharp.
Tool names mix styles: single verbs (authenticate, connect), nouns (marketplace), verb_noun with underscores (report_bug, show_version), and a long Portuguese snake_case name (cnd_imovel_rural_consultar). There is no consistent pattern, and the language mix (English vs Portuguese) adds to the inconsistency.
With 7 tools, the count is within a reasonable range, but only one tool serves the server's stated domain ('CND Imóvel Rural'). The other six are generic platform utilities, making the set feel bloated with meta-tools rather than focused on the certificate service.
For the domain of issuing a negative certificate for a rural property, the single 'cnd_imovel_rural_consultar' tool covers the core operation. There are no obvious missing domain operations (e.g., no need for update or delete). However, the platform tools are unrelated to the domain, which slightly detracts from the overall completeness.