Skip to main content
Glama

Official MCP Registry entry

registry_lookup
Read-onlyIdempotent

Look up an official MCP Registry entry by name, package, or search term to retrieve packages, remotes, TrustedMCP grade, and reported CVEs/GHSA advisories with version impact.

Instructions

Get an official MCP Registry entry ('io.github.owner/repo') with its packages, remotes, TrustedMCP grade if any, and reported security issues (GHSA/CVE advisories, and whether the listed version is affected). Also accepts a package name or search term and picks the best matching entry.

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": {
      "name": "<name>"
    },
    "name": "registry_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesRegistry name like 'io.github.owner/repo', or a package name or search term

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the description's job is to add beyond that — and it does, by disclosing the response contents (packages, remotes, TrustedMCP grade, security advisories and whether the listed version is affected). It also reveals the fuzzy-matching behavior ('picks the best matching entry'), though it is silent on what happens when no entry matches.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the resource and example identifier, with the alternate input mode deferred to the end. Dense but every clause carries information; the parenthetical advisory list is slightly crowded but justified by the return-shape disclosure.

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?

No output schema exists, so the description correctly takes on the burden of describing what comes back, and it covers the notable fields including security advisories. The remaining gap is failure/ambiguity handling for names that match nothing or match multiple entries, which matters given the fuzzy-match behavior it advertises.

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?

With one parameter at 100% schema description coverage, the schema already explains that 'name' accepts a registry name, package name, or search term. The description restates this and adds the useful clarification that a best match is selected, but adds no format, escaping, or ambiguity-resolution detail beyond that.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get an official MCP Registry entry') and enumerates the payload an agent can expect: packages, remotes, TrustedMCP grade, and GHSA/CVE advisories with version-affect status. It does not explicitly differentiate itself from the sibling lookup_server, so it stops short of a 5.

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?

Usage is only implied: the second sentence tells you the input may be a full registry name, a package name, or a search term, which hints at a fuzzy-resolution use case. There is no statement of when to prefer lookup_server or find_alternatives, nor any when-not guidance.

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