Fetch read-only install, config, usage, and package guidance for a HeyClaude entry.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Slug of the entry to get install guidance for. | |
| category | Yes | Category of the entry (e.g. 'mcp', 'skills'). | |
| platform | No | Target platform to tailor the install steps (e.g. 'claude-desktop', 'cursor'). |
| Name | Required | Description | Default |
|---|---|---|---|
| ok | Yes | ||
| policy | 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?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds context that the tool returns guidance for install, config, usage, and package, which aligns with annotations. However, no additional behavioral traits beyond what annotations signal are disclosed.
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, front-loaded sentence with no wasted words. Every part contributes to understanding the tool's purpose.
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?
Given the presence of an output schema and well-documented parameters, the description covers the core function adequately. However, it could briefly clarify the scope of 'guidance' (e.g., what sections are returned) to be more self-contained.
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 coverage is 100% with descriptions for all three parameters. The description does not add meaning beyond the schema; it only summarizes the tool's overall output. Baseline 3 is appropriate as the description adds marginal value.
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 the specific verb 'Fetch' and clearly identifies the resource as 'install, config, usage, and package guidance' for a HeyClaude entry. This distinguishes it from sibling tools like install.setup or install.adapter, which deal with actual installation or adapter configuration.
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 implies usage for retrieving guidance (read-only), but it does not explicitly state when to use this tool versus alternatives such as install.compatibility or install.setup. No exclusions or alternative recommendations are provided.
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 purposes, especially with clear prefixes. However, there is some overlap between entry.safety and entry.trust (both deal with safety/trust metadata), and between registry.recommend and registry.plan (both provide recommendations). The descriptions help differentiate but some ambiguity remains.
All tool names follow a consistent pattern: a domain prefix (entry, install, registry, submission) followed by a descriptive noun, all lowercase with underscores. This makes the surface predictable and easy to navigate.
27 tools is slightly high but reasonable given the broad scope of the HeyClaude registry, which includes browsing, recommending, installing guidance, and submission preparation. The count is appropriate for the server's purpose.
The tool surface is comprehensive, covering search, detail, comparison, safety/trust analysis, install setup for multiple clients, recommendation, and a full submission pipeline (validation, review, schema, etc.). There are no obvious gaps for the intended read-only registry directory functionality.
