Single entrypoint for MCP catalog. action=search returns available tools ordered by relevance. action=describe returns tool schema. action=invoke executes a tool by ID.
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | ||
| action | No | search | |
| queries | No | ||
| tool_id | No | ||
| arguments | No | {} | |
| min_score | No | ||
| force_reindex | No |
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?
The description does disclose key behavior: search orders by relevance, describe returns schema, and invoke executes a tool by ID. But with all annotations set to false or unknown, the description carries the burden, and it omits side effects, authentication needs, and consequences of invoking arbitrary tools.
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 a single tight, front-loaded statement with no filler. Every clause earns its place by specifying a distinct action and return behavior.
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?
This is a multi-action, 7-parameter tool with no output schema. The description explains the routing but not the parameter contract, return shape, or operational risks, so an agent cannot reliably construct correct calls beyond the action switch.
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?
Schema description coverage is 0%, so the description must explain the parameters. It explains action and implies tool_id, but query, queries, arguments, min_score, and force_reindex are left undefined, including the important arguments format and score threshold semantics.
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 names a specific resource (MCP catalog) and a specific verb per action: search returns tools, describe returns schema, invoke executes by ID. It also labels itself as the 'single entrypoint,' which distinguishes it from catalog-adjacent siblings like marketplace and toolkit_info.
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 action= clauses give clear internal usage routing: choose search for tools, describe for schemas, invoke for execution. However, it does not explicitly contrast this tool with siblings or state when not to use it, so the guidance is more implied than explicit.
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.
marketplace and search_tools both cover catalog search, describe, and invoke, making their boundaries unclear. connect and toolkit_info also overlap on reporting connection status, so an agent could easily select the wrong tool for the same task.
All names use lowercase snake_case, but the patterns vary: single-word verbs (authenticate, connect), a noun (marketplace), and compound nouns (toolkit_info). There is no consistent verb_noun convention, though the names remain reasonably readable.
Seven tools is a reasonable size for an MCP platform-management server, and most tools cover distinct operational areas. However, marketplace and search_tools overlap significantly, so the count could be trimmed without losing functionality.
The set covers authentication, connection status, catalog search and execution, toolkit state, version info, and bug reporting, which supports the core platform workflows. The main weakness is that install/uninstall/billing operations are buried inside the marketplace tool description rather than exposed as first-class tools.