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 state readOnly and idempotent. The description adds behavioral details: returns authenticated:true and empty pending[] when all connected, and provides connect_url and per-install URLs when missing credentials. This is beyond annotations, giving clear expectations.
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 concise, using clear conditional statements to explain behavior. It is structured logically and easy to grasp.
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?
Covers main scenarios (all connected, missing credentials) but could mention partial connectivity or other states. Still, it provides enough context for typical use.
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 no parameters (openWorldHint false, empty schema properties). The description implicitly confirms no parameters needed since it just returns status. This is unambiguous.
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, which is specific and distinct from sibling tools like authenticate (which presumably performs authentication) or show_version. It identifies the resource being checked and the type of output.
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 conditional scenarios ('when all providers are connected' vs 'when credentials are missing'), which implies it should be used to check connection state flagged. However, it does not explicitly contrast with alternatives like 'authenticate', which might be a complementary tool. Clear enough context but 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.
The tools are mostly distinct in purpose: authenticate and connect handle credentials, marketplace handles discovery/execution, toolkit_info shows state, ecac_dctf_web_consultar does a specific query, report_bug and show_version are utility functions. However, connect and toolkit_info overlap in reporting connection status, and marketplace's invoke behavior might confuse with directly calling tools like ecac_dctf_web_consultar if not careful.
The naming is inconsistent: most tools use lowercase snake_case or simple verbs (authenticate, connect, marketplace, report_bug, show_version, toolkit_info), but ecac_dctf_web_consultar uses a mixed pattern with underscores and a domain-specific name, breaking the convention. It's readable but not uniform.
7 tools is reasonable for a combined MCP marketplace and specific query server. The count is not excessive, and each tool serves a distinct function, though some like report_bug and show_version are minor utilities.
The surface covers authentication, connection status, marketplace discovery/invocation, toolkit state, and a specific query tool. It lacks obvious operations like uninstall/subscribe are embedded in marketplace, and there's no tool for managing tokens directly (only via authenticate). Overall, the domain is covered adequately, though some marketplace operations are bundled into one mega-tool.