Skip to main content
Glama

HeyClaude — Claude & AI workflow directory

by io.github.JSONbored

registry.updates

Read-onlyIdempotent

List recently added or upstream-updated HeyClaude entries from generated registry metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoFilter to entries carrying this exact tag.
limitNoMaximum entries to return (1–25, default 10).
queryNoKeyword search to narrow the listing.
sinceNoReturn only entries updated after this date, e.g. '2026-05-01'.
categoryNoRestrict to a single category (e.g. 'mcp', 'hooks').
platformNoFilter to entries compatible with this platform.
claimStatusNoFilter by claim or verification status ('unclaimed', 'pending', 'verified', or 'all').
sourceStatusNoFilter by whether the entry's source URL is reachable ('available', 'missing', or 'all').
downloadTrustNoFilter by package download trust level ('first-party', 'external', 'none', or 'all').
hasSafetyNotesNoFilter by whether entries include safety notes ('true', 'false', or 'all').
hasPrivacyNotesNoFilter by whether entries include privacy notes ('true', 'false', or 'all').

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
policyNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed7 schema fields changed
    • addedInput schema / properties / claimStatus
      Added value: +{
+  "description": "Filter by claim or verification status ('unclaimed', 'pending', 'verified', or 'all').",
+  "enum": [
+    "all",
+    "unclaimed",
+    "pending",
+    "verified"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / downloadTrust
      Added value: +{
+  "description": "Filter by package download trust level ('first-party', 'external', 'none', or 'all').",
+  "enum": [
+    "all",
+    "first-party",
+    "external",
+    "none"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / hasPrivacyNotes
      Added value: +{
+  "description": "Filter by whether entries include privacy notes ('true', 'false', or 'all').",
+  "enum": [
+    "all",
+    "true",
+    "false"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / hasSafetyNotes
      Added value: +{
+  "description": "Filter by whether entries include safety notes ('true', 'false', or 'all').",
+  "enum": [
+    "all",
+    "true",
+    "false"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / query
      Added value: +{
+  "description": "Keyword search to narrow the listing.",
+  "maxLength": 240,
+  "type": "string"
+}
    • addedInput schema / properties / sourceStatus
      Added value: +{
+  "description": "Filter by whether the entry's source URL is reachable ('available', 'missing', or 'all').",
+  "enum": [
+    "all",
+    "available",
+    "missing"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / tag
      Added value: +{
+  "description": "Filter to entries carrying this exact tag.",
+  "maxLength": 80,
+  "minLength": 1,
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / platform
      Added value: +{
+  "description": "Filter to entries compatible with this platform.",
+  "maxLength": 80,
+  "minLength": 1,
+  "type": "string"
+}
  3. First observed

TDQS

A4.2/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, making the safety profile clear. The description adds context about the data source ('generated registry metadata') and the nature of updates ('recently added or upstream-updated'), which enriches understanding beyond the 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, concise sentence that front-loads the key action and scope. Every word contributes to understanding, with no wasted text.

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?

For a filterable listing tool with 11 parameters and an output schema, the description is sufficient to convey the core purpose—listing recent updates with filters. It does not detail output format (output schema exists) or behavior corner cases, but it is complete enough given the tool's simplicity.

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 the schema already documents all 11 parameters. The description adds no additional meaning beyond the schema, meeting the baseline expectation but not exceeding it.

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 states 'List recently added or upstream-updated HeyClaude entries from generated registry metadata' which uses a specific verb ('list') and resource ('HeyClaude entries') and adds scope ('recently added or updated'), distinguishing it from sibling tools like registry.list (general listing) and registry.search (search).

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

Usage Guidelines4/5

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

The description implies usage for recent updates ('recently added or upstream-updated') but does not explicitly state when to use versus sibling tools like registry.list or registry.search. No exclusions or alternatives are mentioned, but the context is clear enough for an informed choice.

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