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 indicate read-only, idempotent, non-destructive behavior. The description adds context about return values under different conditions (all connected vs. missing credentials), which provides useful behavioral transparency 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 primary action, and efficiently explains conditional outcomes without wasted words.
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 parameterless tool with no output schema, the description fully explains the return behavior in both connected and missing-credential states. It is complete and sufficient for the tool's simplicity.
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 baseline is 4. The description does not need to explain parameters, and the schema is empty. No additional parameter semantics are required.
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 that the tool returns connection status and URLs, with specific conditional behavior. It distinguishes itself from siblings like authenticate by focusing on status retrieval 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?
The description implies usage for checking connection status but does not explicitly state when to use it versus alternatives like authenticate. It lacks clear exclusions or alternative guidance, so it falls short of a higher score.
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 tools are individually distinct, but the set mixes a single CAFIR-specific query with generic platform utilities (marketplace, connect, authenticate), making it unclear what the server is for. An agent might confuse connect with toolkit_info, and marketplace is an overloaded catch-all.
Names are inconsistent: single-word verbs (authenticate, connect, marketplace), underscore-separated verb_noun (report_bug, show_version, toolkit_info), and a long domain-specific name (cafir_imoveis_rurais_consultar) follow no common pattern.
While 7 tools is a reasonable number in general, only one tool actually addresses the CAFIR domain; the rest are platform housekeeping tools that feel out of place in a server named 'CAFIR', so the count is inflated for its apparent scope.
For a CAFIR-specific server, the only domain operation is a single query by CIB. There is no listing, search, or other rural-property functionality, leaving the core domain severely under-covered. The platform tools are complete, but they are not the intended focus.