Skip to main content
Glama

Stork MCP Directory

stork_search

Read-onlyIdempotent

Find an MCP server for a task. Say the task or product in plain words, for example: query Stripe payments, or browser automation. Results are ranked for an agent: the vendor's own server first, then servers you can connect to that answered Stork's last check. Each result is short: connect (remote URL or npm command, and whether sign-in is needed; null when Stork holds no install method), publisherDomainVerified, toolNames, and check: what Stork's own scheduled request to the endpoint last saw (result: answered | sign_in_required | stream_only | no_answer, lastCheckedAt, toolCount, toolDefinitionTokens = estimated tokens the tool definitions add to your context, toolsLastChangedAt, toolsChangedWithoutVersionChange). check is null for local stdio servers, which Stork cannot run. confidence: weak means nothing listed is a close match. A check is one initialize and one tools/list without an account: it does not prove a tool call works or that the server is safe. Listings that are duplicates of another listing, or that have not answered three checks in a row, are left out.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "stork_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
categoryNo
live_onlyNoOnly servers whose endpoint answered the last check without an account.
transportNo
max_tool_tokensNoOnly servers whose tool definitions are estimated at or under this many tokens.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior5/5

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

Beyond the read-only, open-world, idempotent annotations, the description discloses ranking order, result fields, null connect cases, confidence: weak, and what a check does and does not prove. It also explains exclusions for duplicates and servers that fail three checks, which materially affects how an agent should interpret results.

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?

The description is front-loaded with the purpose and packs substantial semantics into compact sentences. The result-field explanation is dense but mostly earns its place; minor structural improvements could make the long middle sentence easier to scan.

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?

There is no output schema, and the description does a strong job explaining return fields and check semantics. It is still incomplete for a six-parameter search tool because several filtering parameters are undocumented, and sibling routing guidance is absent.

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

Parameters2/5

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

Schema description coverage is only 33%, so the description should carry more parameter meaning. It explains only the query parameter in plain language; the limit, category, live_only, transport, and max_tool_tokens filters are not described or clarified in the tool description.

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?

The description states a specific verb and resource: find an MCP server for a task. It is clear what the tool returns, but it does not explicitly distinguish itself from siblings such as stork_server_details or stork_compare.

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?

It gives useful query guidance with examples and explains that plain task wording works. However, it does not say when to use this search versus stork_server_details, stork_compare, or other siblings, nor does it state when not to use it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources