Skip to main content
Glama
Jackalope-Dev

allmcps-server

by Jackalope-Dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_mcp_servers

Read-only

Search the AllMCPs directory for Model Context Protocol servers by keyword or category, and filter results by transport or verified status to find compatible servers.

Instructions

Search the AllMCPs directory for Model Context Protocol (MCP) servers by keyword or category.

Input Schema

NameRequiredDescriptionDefault
limitNoMax number of results to return (default: 10, max 50)
queryNoSearch term (e.g., "github", "postgres", "slack", "database")
categoryNoOptional category filter. Accepts a directory category name, its plain label, or its slug (e.g. "Databases" or "databases") — call list_mcp_categories for the full list.
transportNoOptional: only hosted (remote HTTP) servers, or only servers you run locally (stdio).
verified_onlyNoOptional: only servers we have seen run — a completed MCP handshake, or a sandbox start that stopped for an API key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.2.0
    • changedInput schema / properties / category / description
      Previous value: -"Optional category name to filter by"New value: +"Optional category filter. Accepts a directory category name, its plain label, or its slug (e.g. \"Databases\" or \"databases\") — call list_mcp_categories for the full list."
    • changedInput schema / properties / limit / description
      Previous value: -"Max number of results to return (default: 10)"New value: +"Max number of results to return (default: 10, max 50)"
    • addedInput schema / properties / transport
      Added value: +{
+  "description": "Optional: only hosted (remote HTTP) servers, or only servers you run locally (stdio).",
+  "enum": [
+    "remote",
+    "stdio"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / verified_only
      Added value: +{
+  "description": "Optional: only servers we have seen run — a completed MCP handshake, or a sandbox start that stopped for an API key.",
+  "type": "boolean"
+}
  2. Addedv2.0.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safe, closed-directory nature is covered structurally. The description adds only the basic keyword/category framing and no further behavioral context (no result ordering, no rate limits, no empty-result behavior), so with annotations present this is a baseline 3.

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?

A single front-loaded sentence with zero waste — purpose and scope are stated first. It is appropriately sized, though its brevity leaves room it could have used for routing guidance.

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?

For a low-complexity, zero-required-param read-only search whose schema is fully self-documenting, the description is sufficient for an agent to select and call it. The absence of an output schema means return-shape details are unstated, which is a minor gap but not blocking.

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 description coverage is 100%, so all five parameters (limit, query, category, transport, verified_only) are fully documented in the schema. The description's 'by keyword or category' merely restates query/category and adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 (Search), resource (AllMCPs directory / MCP servers), and scope (by keyword or category). It's immediately clear what the tool does, though it doesn't explicitly differentiate itself from adjacent siblings like list_mcp_categories or get_mcp_alternatives.

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 agent infers you call this when looking for servers. There is no explicit when-to-use/when-not guidance, and no mention of alternatives such as list_mcp_categories for pure browsing, even though the schema references that tool for category values.

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