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 establish read-only, idempotent, non-destructive behavior. The description adds useful context about return values (authenticated:true, pending[], connect_url) under different conditions, going beyond what annotations provide.
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, front-loaded with the primary purpose and then detailing conditional outcomes. Every word earns its place with no redundancy.
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 simple 0-parameter tool with robust annotations, the description explains the main response states. It could be more explicit about partial connection scenarios, but overall it is sufficient for correct usage.
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, and schema coverage is vacuously 100%. Baseline for zero-parameter tools is 4, and the description correctly adds no unnecessary parameter details.
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 verbs and resource. It distinguishes itself from sibling tools like authenticate, which is an action, while this is a status check.
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 contextual usage information by describing behavior in different states (all connected vs. missing credentials), implying when to call it to check connectivity. However, it lacks explicit exclusions or direct comparison to alternative tools.
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.
Each tool has a clearly distinct purpose: authentication, connection status, marketplace operations, bug reporting, version info, toolkit state, and vehicle consultation. No two tools overlap in functionality, so an agent can reliably select the right one.
Tool names are inconsistent, mixing English verbs (authenticate, connect, marketplace), verb+noun (report_bug, show_version), noun+noun (toolkit_info), and a Portuguese snake_case domain term (veiculo_estadual_consultar). No consistent convention is used across the set.
Seven tools is a moderate count, but six of them are generic platform utilities unrelated to the server's stated vehicle-consultation purpose. The domain-specific surface is minimal, making the server feel padded with infrastructure tools.
For the domain of vehicle consultation, the single tool covers the core needs (lookup by plate with debts and situation). There are minor potential gaps, such as distinguishing different query types (e.g., by VIN), but the current surface is workable for a read-only consultation service.