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 read-only and idempotent hints. The description adds value by explaining response variations (authenticated:true vs connect_url) and the presence of pending[]. This goes beyond annotations and gives useful conditional 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 well-structured sentences, front-loaded with the primary purpose and then providing conditional details without unnecessary fluff. Every sentence earns its place.
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?
Given the simple zero-parameter tool and no output schema, the description covers the main scenarios (all connected vs credentials missing). However, it omits potential edge cases like partial connection states, leaving minor ambiguity, so it is not quite a 5.
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 description has no parameter details to add. The baseline for 0 params is 4, and the description does not need to compensate for missing schema coverage since there is nothing to document.
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, using a specific verb and resource. It distinguishes itself from siblings like authenticate by focusing on status checking rather than the authentication action itself.
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 provides clear context on when to use it: to check if all providers are connected and to get URLs when credentials are missing. It does not explicitly mention alternatives or when-not-to-use, but the conditional behavior implies its role in a connection workflow.
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.
Several platform-management tools overlap in purpose: authenticate and connect both deal with connection state, while show_version and toolkit_info both return platform status. The marketplace tool is an overloaded catch-all that handles searching, invoking, installing, and billing, making it unclear when to use it versus the other tools.
Naming conventions are mixed: some tools follow verb_noun patterns (authenticate, connect, report_bug, show_version), while others are bare nouns (marketplace, toolkit_info). Additionally, the only domain-specific tool uses Portuguese (veiculo_nacional_consultar) while the rest use English, creating a language inconsistency.
The server is named 'Consulta Veicular Nacional' and appears focused on vehicle lookup, yet only 1 of 7 tools actually performs that function. The other 6 are generic platform utilities unrelated to the stated purpose, making the tool count feel bloated and off-target for the server's apparent scope.
For the core domain of vehicle consultation, the single tool veiculo_nacional_consultar provides the essential lookup-by-plate capability with no obvious missing operations. Since it is a read-only public data consultation, CRUD coverage is unnecessary, and the vehicle-related surface appears complete. The extra platform tools do not fill any domain-specific gap.