Skip to main content
Glama
Sign In
mcp-registry

mcp-registry

by daedalus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_mcp_servers

Retrieve a paginated list of MCP servers from the registry. Specify limit and cursor to navigate through results.

Instructions

List MCP servers from the MCP Registry with pagination support.

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": "list_mcp_servers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of servers to return (1-100, default: 50).
cursorNoPagination cursor for retrieving next set of results.
registry_urlNoBase URL of the MCP Registry API (default: production).https://registry.modelcontextprotocol.io

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior2/5

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

No annotations provided, and the description only mentions 'list' and 'pagination support' without disclosing behavioral traits like read-only nature, rate limits, error handling, or output structure beyond what the output schema provides.

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 a single concise sentence with no redundancy, front-loading the core purpose effectively.

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?

Given the rich input schema (100% coverage) and existence of an output schema, the description is largely complete for a paginated list operation, though it could briefly mention the default behavior or scope.

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% and all parameters have descriptions; the description adds minimal value beyond stating 'pagination support', which is already implied by the cursor and limit parameters.

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 the action 'list' and the resource 'MCP servers from the MCP Registry' with pagination support, distinguishing it from sibling tools like 'get_mcp_server' (single server) and 'search_mcp_servers' (search).

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 implies usage for listing with pagination but does not explicitly state when to use this tool versus alternatives (e.g., search or get single server), leaving room for ambiguity.

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

Deploy Server

Other Tools