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 read-only, idempotent, and non-destructive behavior. The description adds useful conditional context: authenticated state vs. missing credentials and the corresponding URLs. It does not contradict the annotations and provides meaningful behavioral detail beyond the structured metadata.
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, immediately states the core purpose, and then provides the two relevant outcome states without any filler. Every sentence contributes useful information.
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?
There is no output schema, but the description covers the two return states and the URL fields the caller can expect. It does not specify the exact structure of per-install URLs, but for a simple status-check tool with zero parameters and clear annotations, this is adequate.
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 there is no parameter documentation burden. The 100% schema coverage and absence of required inputs are already clear, and the description 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 uses a specific verb and resource ('Returns connection status and URLs') and explains conditional return behavior, clearly distinguishing this status-check tool from siblings like authenticate. The two state-based outcomes further clarify its role.
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 gives clear context on when the tool is useful and what results to expect in different states, but it does not explicitly contrast it with alternatives such as authenticate or provide explicit 'use when' language. The behavioral context is strong enough for an agent to infer the right usage.
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 clearly distinct purposes (authentication, connection status, marketplace, version, consultation). However, connect and toolkit_info both return connection-related status, creating slight overlap. Marketplace is a mega-tool with many sub-actions, but its description is thorough enough to avoid confusion.
Naming conventions are inconsistent: some tools are verbs (authenticate, connect, report_bug), some are nouns (marketplace, toolkit_info), and one is a Portuguese compound verb (sintegra_rs_consultar). There is no consistent verb_noun pattern, and the language mix further weakens predictability.
With 7 tools, the set is well-scoped for a platform management server. Each tool serves a distinct high-level function, and the count is within the ideal range without feeling bloated or sparse.
The tool surface covers core platform operations: authentication, connection status, marketplace interactions (search/invoke/install), bug reporting, version display, and toolkit state. Minor gaps exist, such as no explicit disconnect or dedicated credential management beyond what marketplace/connect offer, but agents can work around these.