Skip to main content
Glama

Registry Lookup

registry_lookup
Read-onlyIdempotent

Query threat intelligence registry to retrieve risk level, verification status, credential requirements, and known tools for MCP servers. Returns a JSON entry or indicates not found.

Instructions

Query the agent-bom MCP server threat intelligence registry.

    Look up risk level, known tools, credential requirements, and
    verification status for known MCP servers. The registry contains
    109+ servers with security metadata.

    Args:
        server_name: MCP server name to look up (e.g. "filesystem",
                     "@modelcontextprotocol/server-github").
        package_name: Package name to search for (e.g. "mcp-server-sqlite").
                      At least one of server_name or package_name is required.

    Returns:
        JSON with registry entry: risk_level, verified, tools,
        credential_env_vars, risk_justification. Returns found=false
        if not found.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
server_nameNoMCP server name to look up, e.g. 'filesystem', '@modelcontextprotocol/server-github'.
package_nameNoPackage name to search for, e.g. 'mcp-server-sqlite'. At least one of server_name or package_name is required.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds value by detailing the return structure (risk_level, verified, etc.) and the behavior when a server is not found (found=false). No contradictions with 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 concise and well-structured: a brief first line, followed by a paragraph, then Args and Returns sections. Every sentence serves a purpose, and the most important information (purpose) is front-loaded.

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?

The description fully covers the tool's purpose, parameters, and return format. Given the presence of an output schema, the description could have omitted return details, but it includes them for clarity. It also provides contextual info (109+ servers) and parameter constraints.

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 coverage is 100% with descriptions for both parameters. The description repeats these descriptions in the Args section and adds examples (e.g., 'filesystem', 'mcp-server-sqlite'). This is helpful but does not provide significant additional meaning 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 it queries a specific registry (agent-bom MCP server threat intelligence) and lists the data fields returned (risk level, tools, credentials, verification). It distinguishes itself from sibling tools like intel_lookup by being focused on MCP server security metadata.

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 provides clear context on what to use the tool for (look up MCP server details) and specifies that at least one parameter is required. However, it does not explicitly mention when not to use it or provide alternative tools for similar lookups.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/msaad00/agent-bom'

If you have feedback or need assistance with the MCP directory API, please join our Discord server