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 mark it read-only and idempotent; the description adds valuable detail about response fields (authenticated, pending[], connect_url) and conditions, going 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?
Two concise sentences: the first states the primary purpose, the second explains conditional behavior. No fluff; every word adds value.
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 stateless, parameterless tool, the description covers return values and key edge cases (credentials missing). It lacks minor details like response format or error codes but is largely complete given low complexity.
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?
There are zero parameters, and schema coverage is 100% (vacuously). Per rubric, baseline is 4. No additional parameter info 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' with specific behavior for connected and missing-credential cases, distinguishing it from siblings like 'authenticate' and 'show_version'.
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 is implied through the description of scenarios (all connected vs missing credentials), but no explicit alternatives or when-not-to-use guidance is given compared to siblings.
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 generic platform tools (authenticate, connect, marketplace, etc.) rather than domain-specific, and 'marketplace' explicitly mentions CPF queries which could be confused with the BCB consult tool. 'connect' and 'toolkit_info' also overlap in providing status information.
The naming is highly inconsistent: most tools use English imperative verbs (authenticate, connect, report_bug, show_version) or nouns (marketplace, toolkit_info), while the only domain-specific tool uses a Portuguese noun phrase with underscore format (bcb_valores_receber_consultar). No clear pattern across the set.
Seven tools is not inherently excessive, but six of them are generic platform management features unrelated to the server's stated purpose of accessing BCB values. The count is inflated with irrelevant tools, making the server poorly scoped for its intended domain.
From a domain perspective, the single BCB consult tool covers the core need for checking 'valores a receber'. However, there is no option for related operations (e.g., scheduling, detailed reports), and the included generic tools do not contribute to domain completeness. Overall, the surface is minimal but not severely incomplete for a simple query.