HeyClaude — Claude & AI workflow directory

registry.search

Read-onlyIdempotent

Search read-only HeyClaude registry entries by query, category, exact tag, and skill platform compatibility.

Input Schema

TableJSON Schema

Name	Required	Description
`tag`	No	Return only entries carrying this exact tag.
`limit`	No	Maximum number of results to return (1–25, default 10).
`query`	No	Keywords to search for in entry titles, descriptions, and tags.
`category`	No	Restrict results to this category (e.g. 'mcp', 'skills', 'hooks').
`platform`	No	Restrict to entries compatible with this platform (e.g. 'claude-desktop', 'cursor').
`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

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description reiterates 'read-only' but adds no new behavioral details (e.g., pagination, rate limits, result ordering). With high annotation coverage, the description does not need extensive context but fails to add extra value beyond annotations.

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?

The description is a single, front-loaded sentence that efficiently communicates the purpose. No extraneous words or redundancy. It earns its place with clear, direct language.

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 (not shown), the description does not need to explain return values. The tool has 10 parameters with full schema descriptions, so the description's summary suffices. Minor missing guidance on combining filters, but overall adequate for a search tool.

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 description coverage is 100%, so baseline is 3. The description summarizes a subset of parameters (query, category, tag, platform) but does not add new meaning or examples beyond what the schema already provides. No compensation needed for gaps.

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 specifies the verb 'Search', the resource 'read-only HeyClaude registry entries', and the search dimensions (query, category, exact tag, platform compatibility). It clearly distinguishes from siblings like registry.list or registry.recommend by emphasizing the search functionality.

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 implies usage for searching registry entries but does not explicitly state when to use this tool versus alternatives (e.g., registry.list for full listing, registry.recommend for recommendations). No exclusions or when-not-to-use guidance is provided.

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.search

Input Schema

Output Schema

TDQS

Glama MCP Gateway

TDQS

Resources