Skip to main content
Glama

Look up a service by name

search_registry
Read-onlyIdempotent

Search the Agent Nexus registry when you already know the service, product, vendor, slug or endpoint you are looking for. Use this for a targeted lookup, not for discovering a solution to a broad task; for a plain-language goal, use discover_capabilities instead. Matches literal text only and does not interpret intent. Optionally narrow the search by category. Returns {count, results[]} containing summary records with slug, name, category, summary, endpoint and trust fields. Results are alphabetical, not ranked by relevance. There is no pagination beyond the limit parameter: increase limit (maximum 50) or narrow the query when needed. Use get_entry to inspect the full record of a relevant result. An empty results[] is a valid answer, not an error. Read-only and side-effect free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
limitNoUpper bound on entries returned, 1-50, default 10. Results are ordered by name, not by relevance, so a small limit on a broad keyword can hide better matches — raise it or use discover_capabilities when you are ranking candidates.
queryNoLiteral substring, max 120 chars, matched case-insensitively against name, summary, endpoint and slug — a product name ('resend'), a vendor, a slug fragment or a host ('api.stripe.com'). Single terms work best: the whole string is matched as one substring, so 'send email' finds nothing unless those words appear together. The characters % , ( ) are stripped. An empty query (the default) returns the first entries in name order, which is a browse, not a search.
categoryNoOptional filter, exactly one of 'api', 'mcp' or 'cli' (see list_categories). Combined with query as AND. Omit to search all three layers.

Output Schema

NameRequiredDescriptionDefault
countYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Restrict results to one interface category."New value: +"Optional filter, exactly one of 'api', 'mcp' or 'cli' (see list_categories). Combined with query as AND. Omit to search all three layers."
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of entries to return (1-50)."New value: +"Upper bound on entries returned, 1-50, default 10. Results are ordered by name, not by relevance, so a small limit on a broad keyword can hide better matches — raise it or use discover_capabilities when you are ranking candidates."
    • changedInput schema / properties / query / description
      Previous value: -"Keyword matched against name, summary, endpoint or slug."New value: +"Literal substring, max 120 chars, matched case-insensitively against name, summary, endpoint and slug — a product name ('resend'), a vendor, a slug fragment or a host ('api.stripe.com'). Single terms work best: the whole string is matched as one substring, so 'send email' finds nothing unless those words appear together. The characters % , ( ) are stripped. An empty query (the default) returns the first entries in name order, which is a browse, not a search."
  2. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of entries to return (1-50)."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "count": {
      +      "type": "number"
      +    },
      +    "results": {
      +      "items": {},
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "count",
      +    "results"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.