Skip to main content
Glama

find_mcps

Discover MCP servers matching your integration needs. Input any capability like database access or API management to get ranked results.

Instructions

Find MCP servers by capability need. Use this when you need to discover MCP servers for specific integrations (e.g., databases, APIs, cloud services). Returns MCP servers ranked by capability match.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
needYesWhat capability you need (e.g., 'Postgres database access', 'Slack messaging', 'GitHub repository management')
limitNoMax results

Implementation Reference

  • src/index.ts:448-465 (registration)
    Registration of the 'find_mcps' tool with the MCP server, including its schema (parameters: need, limit) and description.
    server.tool(
      "find_mcps",
      "Find MCP servers by capability need. Use this when you need to discover MCP servers for specific integrations (e.g., databases, APIs, cloud services). Returns MCP servers ranked by capability match.",
      {
        need: z.string().min(2).max(500).describe("What capability you need (e.g., 'Postgres database access', 'Slack messaging', 'GitHub repository management')"),
        limit: z.number().min(1).max(20).default(5).describe("Max results"),
      },
      async ({ need, limit }) => {
        log("find_mcps", need);
        try {
          const data = await searchAPI(`MCP server for ${need}`, { limit, type: "mcp" });
          const text = formatResults(data);
          return { content: [{ type: "text" as const, text }] };
        } catch (err) {
          return { content: [{ type: "text" as const, text: `Error: ${err instanceof Error ? err.message : String(err)}` }], isError: true };
        }
      }
    );
  • Handler function for 'find_mcps' tool. Logs the query, calls searchAPI with the need prefixed by 'MCP server for' and type filtered to 'mcp', formats results via formatResults, and returns text content or an error.
    async ({ need, limit }) => {
      log("find_mcps", need);
      try {
        const data = await searchAPI(`MCP server for ${need}`, { limit, type: "mcp" });
        const text = formatResults(data);
        return { content: [{ type: "text" as const, text }] };
      } catch (err) {
        return { content: [{ type: "text" as const, text: `Error: ${err instanceof Error ? err.message : String(err)}` }], isError: true };
      }
    }
  • Input schema for 'find_mcps' tool: 'need' (string, 2-500 chars) and 'limit' (number, 1-20, default 5).
    {
      need: z.string().min(2).max(500).describe("What capability you need (e.g., 'Postgres database access', 'Slack messaging', 'GitHub repository management')"),
      limit: z.number().min(1).max(20).default(5).describe("Max results"),
    },
Behavior4/5

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

With no annotations, the description adds value by stating that results are 'ranked by capability match,' which is not in the schema. It does not disclose any side effects, authentication needs, or rate limits, but for a read-only search tool, this is adequate.

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, no fluff. The first sentence states the core purpose, the second provides usage context and a key output detail. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description lacks an output schema and does not fully detail the return structure beyond 'MCP servers ranked by capability match.' An agent might need to know what fields each server contains to use the results effectively.

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%, so the description does not need to add much. It restates the 'need' parameter's purpose but does not provide additional semantic meaning beyond what the schema already offers.

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 states it finds MCP servers by capability need, which is a specific verb and resource. It clearly distinguishes from sibling tools like find_stack or search by focusing on capability-based discovery of MCP servers.

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?

Explicitly says 'Use this when you need to discover MCP servers for specific integrations,' providing a clear usage context. However, it does not mention when not to use it or compare with alternatives like search or resolve_capability.

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/Savirinc/unfragile-mcp-server'

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