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 readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds valuable behavioral detail by specifying the exact return states: authenticated:true with empty pending[] when connected, and connect_url plus per-install URLs when credentials are missing.
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 main purpose, and every sentence adds meaningful conditional behavior. No 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?
With no parameters and no output schema, the description carries the full burden of explaining return values. It covers both primary states (all connected vs. missing credentials) and is complete for a simple status-checking tool.
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 parameter semantics; it appropriately focuses on output behavior instead.
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 a specific verb and resource. It differentiates from siblings like authenticate by focusing on status reporting rather than initiating 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 provides clear context for when to use the tool: to check connection status and retrieve URLs when credentials are missing or all providers are connected. It does not explicitly name alternatives or state when not to use it, but the status-vs-authenticate distinction is implied.
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 marketplace tool is overloaded with many subcommands (search, describe, invoke, install, subscribe, prompts), which overlaps with report_bug, toolkit_info, and even authenticate/connect. The single vehicle tool stands apart, but the meta-tools have blurry boundaries.
Names mix bare verbs (authenticate, connect), verb_noun pairs (report_bug, show_version), and noun phrases (marketplace, toolkit_info, veiculo_dados). The pattern is inconsistent, and languages are mixed (English vs Portuguese).
Seven tools is a reasonable number, but six of them are generic MCP-platform management utilities unrelated to the server's apparent 'Veículo' vehicle purpose. Only one tool actually provides vehicle data, making the set poorly scoped for its intended domain.
For a vehicle-data server, only one lookup operation exists with no other vehicle-related capabilities. The remaining tools cover platform plumbing but not the vehicle domain, leaving significant gaps in what an agent would expect from a 'Veículo' server.