Skip to main content
Glama

HeyClaude — Claude & AI workflow directory

by io.github.JSONbored

registry.recommend

Read-onlyIdempotent

Answer 'what should I use to do X' in one call. Given a plain-language task (and optional platform/category), returns the best-match HeyClaude entries ranked by fit — each with why it fits, trust summary, disclosed safety/privacy notes, and an inline install block — plus a topPick and a consolidated installPlan. Unlike workflow.plan it does not force category diversity; it returns the genuinely best matches. Collapses the search → compare → detail → asset loop into a single answer-shaped response.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskYesPlain-language description of what you want to accomplish, e.g. 'review pull requests in Claude Code' or 'connect to a Postgres database'.
limitNoMaximum recommendations to return (default 3).
categoryNoRestrict recommendations to a single category.
platformNoRestrict to entries compatible with this platform.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
policyNo

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds detailed behavioral context: returns ranked matches with fit reasons, trust summary, safety/privacy notes, inline install block, topPick, and installPlan. No 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?

Every sentence earns its place: purpose, return details, differentiation from sibling, and summary of benefits. Front-loaded and efficient with no waste.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity, output schema existence, and many siblings, the description covers purpose, usage, behavioral details, and differentiation. It is self-contained and sufficient for an agent to select and invoke correctly.

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

Parameters4/5

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

Schema has 100% coverage with clear descriptions for all 4 parameters. The description adds value by rephrasing task as 'plain-language' and noting platform/category as optional, slightly enhancing understanding 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 the tool answers 'what should I use to do X' in one call, using a plain-language task. It also explicitly contrasts with registry.plan (mentioned as workflow.plan) to differentiate its behavior, making the purpose distinct from siblings.

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

Usage Guidelines5/5

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

The description specifies when to use (given a plain-language task) and explicitly contrasts with workflow.plan by noting it does not force category diversity, providing clear guidance on alternative 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 toolsInspect
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.

Resources