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=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds value by describing the two output states (connected vs. missing credentials) and the URLs returned, which goes beyond the structured 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, front-loaded with the core purpose and then concise state-dependent behavior. No filler or repetition.
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?
The description covers the main behavioral outcomes (connected vs. missing credentials) and mentions return components (authenticated, pending[], connect_url, per-install URLs). While it doesn't mention edge cases like partial connection, the tool is simple enough that this is adequate without a dedicated output schema.
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 per the baseline rule, a score of 4 is appropriate. The description does not need to explain parameters since there are none.
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 uses a specific verb ('Returns') and resource ('connection status and URLs'), clearly distinguishing it from siblings like authenticate and show_version. It also adds state-dependent details, reinforcing its purpose.
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 what the tool returns (status and URLs) and implies it should be used to check connection state, not to perform authentication. However, it does not explicitly state when to use this tool over alternatives like authenticate, so it lacks explicit exclusions.
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 roles: authentication, connection status, marketplace, feedback, version, toolkit state, and the domain query. However, authenticate, connect, and toolkit_info all touch on connection/auth concepts, which could cause initial confusion.
The platform tools use varied patterns (single-word verbs, nouns, verb_noun combinations), while the domain tool uses a long descriptive snake_case name. This mix is readable but not uniform.
Seven tools is within a reasonable range, but six are generic platform utilities and only one serves the apparent domain purpose. The count feels inflated relative to the domain scope.
The domain surface is extremely thin with a single query operation. There are no other process-related endpoints (e.g., search, details, movements), making it a minimal but possibly complete read-only lookup.