HeyClaude — Claude & AI workflow directory

registry.list

Read-onlyIdempotent

List read-only HeyClaude entries with bounded pagination and optional category, platform, tag, and query filters.

Input Schema

TableJSON Schema

Name	Required	Description
`tag`	No	Filter to entries carrying this exact tag.
`limit`	No	Number of entries per page (1–25, default 20).
`query`	No	Keyword search to narrow the listing.
`offset`	No	Pagination offset for large result sets (0–5000).
`category`	No	Category to list entries from (e.g. 'mcp', 'skills', 'agents').
`platform`	No	Filter to entries compatible with this platform.
`claimStatus`	No	Filter by claim or verification status ('unclaimed', 'pending', 'verified', or 'all').
`sourceStatus`	No	Filter by whether the entry's source URL is reachable ('available', 'missing', or 'all').
`downloadTrust`	No	Filter by package download trust level ('first-party', 'external', 'none', or 'all').
`hasSafetyNotes`	No	Filter by whether entries include safety notes ('true', 'false', or 'all').
`hasPrivacyNotes`	No	Filter by whether entries include privacy notes ('true', 'false', or 'all').

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	Yes
`policy`	No

TDQS

A4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds value by specifying bounded pagination (limit 1–25, offset 0–5000) and listing filter categories, complementing the safety profile without contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single 13-word sentence that is front-loaded with essential information: list operation, read-only, bounded pagination, and optional filters. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

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, high schema coverage, and annotations, the description adequately explains the tool's purpose and key constraints. It lacks details on sorting order or definition of 'HeyClaude entries' but is sufficient for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with detailed descriptions for all 11 parameters. The description adds marginal value by mentioning 'category, platform, tag, and query filters' but does not provide additional meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it lists read-only HeyClaude entries with bounded pagination and optional filters, distinguishing it from sibling tools like registry.search and registry.stats.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not explicitly specify when to use this tool versus alternatives like registry.search. Usage context is implied but lacks clear guidance on selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All HeyClaude — Claude & AI workflow directory tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0

Disambiguation4/5

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.

Naming Consistency5/5

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.

Tool Count4/5

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.

Completeness5/5

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.

registry.list

Input Schema

Output Schema

TDQS

Glama MCP Gateway

TDQS

Resources