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 behavior. The description adds valuable context by explaining the conditional return states (authenticated:true with empty pending[] vs connect_url when credentials are missing), 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 main purpose, and no filler. Every sentence adds meaningful behavioral detail.
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 zero-parameter status tool with strong annotations, the description covers the main return cases and URL behavior. It does not explicitly describe partial-connection states, but the mention of pending[] implies that scenario, so the description is largely complete.
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 an empty input schema, so there is nothing for the description to explain. Baseline 4 applies for parameterless tools.
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?
Description clearly states it returns connection status and URLs, with specific conditional behavior for connected vs missing credentials. This distinguishes it from sibling 'authenticate', which would perform authentication rather than report status.
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?
Usage is implied: use this tool to check connection status and get URLs. However, it does not explicitly mention when not to use it or contrast it with alternatives like authenticate or toolkit_info.
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 discovery/execution, bug reporting, version check, specific data consultation, and toolkit overview. No overlapping functions that would cause an agent to misselect.
Tool names follow no consistent pattern: single verbs (authenticate, connect), compound verbs (report_bug, show_version), a bare noun (marketplace), and a domain-specific descriptive name (sintegra_df_consultar). The mixture of styles makes it unpredictable.
7 tools is well within the ideal range (3-15) and each serves a necessary function for a server that manages platform connections and offers a specific data query. The scope is appropriately matched to the tool count.
The surface covers the core lifecycle: authentication, connection status, tool discovery/execution, billing management, feedback, version, and toolkit state. A minor gap such as no explicit disconnect or logout is non-critical, but the main workflows are supported.