Skip to main content
Glama

Search the registry

search_registry
Read-onlyIdempotent

Search skills, agents, and commands across all corpora registered on this machine and return ranked hits with their source to find entries beyond one corpus.

Instructions

Search skills, agents and commands across every corpus registered on this machine. Returns ranked hits with the source each came from. Not covered by search_library, which searches one corpus only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_registry"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindsNoRestrict to these entry kinds. Every kind when omitted.
limitNoMaximum hits.
queryYesFree-text query.
sourcesNoRestrict to these source ids. Every source when omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the result ordering ("ranked hits") and that each hit carries its originating source, which tells the agent how to interpret and attribute results.

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?

Three short sentences, with the core action and scope front-loaded and the sibling comparison last. Every sentence carries distinct information and none repeats the name or title.

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 four-parameter read-only search with full schema coverage and annotations, the definition supplies the missing pieces: corpus-wide scope, ranked ordering and source attribution on results. No output schema exists, and the description gives enough of the return shape to call the tool correctly; only per-parameter behavior remains undocumented, which the schema handles.

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%, and the schema already documents query, kinds, sources and limit, including their defaults. The description adds no syntax, format or interaction detail for any of these parameters, so the baseline 3 applies.

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 gives a specific verb and resource ("Search skills, agents and commands") plus the scope ("across every corpus registered on this machine"), so an agent knows exactly what is being searched. It also states the return shape ("ranked hits with the source each came from"), which separates it from a plain listing tool.

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?

It explicitly routes the agent away from the narrower alternative: "Not covered by search_library, which searches one corpus only," which tells the agent to pick this tool when the scope is cross-corpus. There is no explicit when-not-to-use or prerequisite guidance beyond that comparison, so it falls just short of the top score.

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