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 readOnly, idempotent, and non-destructive hints. The description adds valuable scenario-specific output details, such as the 'authenticated:true' and 'pending[]' fields, and the behavior when credentials are missing, which goes 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 sentences, no wasted words, the key information is front-loaded with the purpose stated immediately.
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 read-only status tool with no output schema, the description covers the main states (connected, missing credentials) sufficiently. It is complete enough for an agent to know what to expect.
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 trivially complete. The description correctly does not mention parameters, and the baseline for 0 params is 4 since no compensation 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, using the specific verb 'Returns.' It distinguishes itself from siblings like 'authenticate' by focusing on status rather than auth actions.
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. It describes conditional scenarios (all connected vs. credentials missing) but gives no direct comparison to sibling 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.
Most tools have distinct purposes, but authenticate and connect both relate to authentication and connection status, which could cause confusion. Marketplace is a catch-all for many sub-functions, making it unclear when to use it versus other tools.
Tool names are inconsistent: some are English verbs (authenticate, connect), some are nouns (marketplace, toolkit_info), and one is a Portuguese snake_case function (dap_pronaf_pf_consultar). There is no consistent verb_noun or stylistic pattern.
Seven tools is a reasonable number for a server that combines platform utilities with a domain-specific query. However, the marketplace tool is a mega-tool that could be split into multiple tools, slightly inflating the effective surface.
The server covers platform operations well (auth, connection, version, bug reporting, toolkit info) but lacks domain-specific operations beyond the single consultation tool. There are no update or delete operations for DAP data, but that may be outside the server's intended scope.