Skip to main content
Glama

registry

by com.policylayer

search_registry

Search the PolicyLayer registry of published MCP servers by name, slug or package substring. Returns candidate matches with risk grade, identity confidence (verified / unverified / mismatch — mismatch means it claims to be an official server with no verifiable link to the brand) and tool count — follow up with check_mcp_server on the match you meant.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax matches to return (1-20, default 10).
queryYesSubstring to match against slug, name and packages.

TDQS

A4.5/5.0
Behavior4/5

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

Discloses return fields (risk grade, identity confidence, tool count) and explains the meaning of 'mismatch'. No annotations, so description carries full burden; sufficiently transparent for a read-only search tool.

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?

Two sentences, front-loaded with purpose, no wasted words. Every sentence contributes value.

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?

Given no output schema, the description fully explains return values and follow-up action. Completely adequate for a search tool with 2 parameters and clear sibling tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds meaning beyond schema by explaining that query is matched against name, slug, and packages, and that limit controls max matches. Schema already describes parameters, but description adds context.

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?

Clearly states it searches the PolicyLayer registry by name, slug, or package substring. Distinguishes from sibling tools by explicitly mentioning follow-up with check_mcp_server.

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?

Provides explicit follow-up action (check_mcp_server) for the intended match, giving context on when to use this tool versus alternatives. Lacks explicit when-not but the context is clear.

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

All registry 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

A4.3/5.0
Disambiguation5/5

Each tool has a distinct and clearly separated purpose: checking single servers, batch checking multiple servers, checking a specific tool on a server, accessing change events, and searching the registry. No overlap or ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern: check_mcp_server, check_mcp_stack, check_tool, get_change_events, search_registry. The verb 'check' is used for three tools but the nouns differentiate them clearly.

Tool Count5/5

Five tools is well-scoped for a registry server. It covers the essential operations (search, single check, batch check, tool-level check, change feed) without being overwhelming or too sparse.

Completeness4/5

The tool surface covers the core functionality of registry lookup and checking. While there is no explicit 'register' tool, the check_mcp_server tool implicitly queues unknown servers. Minor gap: no dedicated tool to list all servers or get a single server's summary without a search.

Resources