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?
Beyond the readOnly/idempotent annotations, the description explains behavior in both success ('authenticated:true') and failure/missing-credential cases, including the returned URLs. This provides clear insight into tool behavior.
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 concise sentences with no redundant information, clearly structured and easy to parse.
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?
Without an output schema, the description fully explains the return value (connection status and URLs) and covers the key edge case of missing credentials, making it complete for practical use.
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 no parameters, so the baseline is 4. The description does not need to explain parameters, and the schema already covers 100% of them (none).
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 details about two output scenarios. This distinguishes it from siblings like 'authenticate' which likely performs a different action.
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 over alternatives. No direct comparison to sibling tools like 'authenticate' or 'marketplace' is provided.
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 mostly distinct in purpose: authenticate, connect, marketplace, report_bug, show_version, toolkit_info, and the domain-specific mpt_ba_cnf_consultar. There is minor overlap between connect (returns connection status and URLs) and toolkit_info (returns toolkit state including connection status), but each has a broader scope, so confusion is unlikely.
Tool names are inconsistent: most are English single-word or camelCase (authenticate, connect, marketplace, report_bug, show_version, toolkit_info), while the only domain-specific tool is in Portuguese with underscores (mpt_ba_cnf_consultar). This mix of languages and conventions breaks the pattern.
Seven tools is within the typical well-scoped range. However, most are generic MCP.AI platform support tools, with only one tool directly serving the stated domain (Certidão Negativa). This slightly dilutes the server's apparent purpose but is not excessive.
For the domain of querying negative certificates, the single mpt_ba_cnf_consultar tool covers the core operation, and the supporting platform tools handle auth, connection, and state. There are no obvious missing operations for a simple query service, though one might expect a history or listing tool, which is absent.