Fetch read-only category examples and templates for faster, more accurate HeyClaude submissions.
| Name | Required | Description | Default |
|---|---|---|---|
| category | No | Category to fetch submission examples for. Returns cross-category examples if omitted. |
| 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 'Read-only' which aligns but does not provide additional behavioral context beyond what annotations cover. No contradictions.
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 clear sentence with no unnecessary words. It is front-loaded and efficient.
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 tool's simplicity (one optional parameter, complete annotations, and an output schema), the description fully covers what the tool does and its behavior. No missing information.
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% and the parameter 'category' already includes a description stating it returns cross-category examples if omitted. The tool description does not add any parameter information beyond the schema.
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?
Description clearly states the verb ('Fetch'), the resource ('category examples and templates'), and the context ('for faster, more accurate HeyClaude submissions'). It is specific and distinguishes from sibling tools like submission.guidance or submission.schema by specifying it returns examples/templates.
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 does not explicitly state when to use this tool over alternatives. It implies its use for obtaining examples/templates but lacks guidance on when to choose it over sibling tools like submission.guidance or submission.prepare.
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.
