Skip to main content
Glama

Stork: search, scrape and docs

stork_find_server

Read-only

Find an MCP server for a task or product (for example: Stripe payments, browser automation). Returns how to connect, whether its endpoint answered Stork's last check, how many tokens its tool definitions cost, and what Stork's own test calls saw. Use it when the user wants a tool installed, not for web search.

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_find_server"
  }
}

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

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real value on top by enumerating what comes back: connection info, last-check endpoint status, tool-definition token cost, and results of Stork's own test calls. It says nothing about rate limits or result freshness beyond 'last check', which keeps it below a 5.

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?

Three sentences, front-loaded with the purpose before the return-value list and the exclusion. The middle sentence is a long enumeration but each item is genuinely informative for a discovery tool, so little is wasted.

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?

With no output schema, the description usefully covers return contents, and it states the read-only/open-world nature via annotations. However, for a six-parameter discovery tool with 33% schema coverage, it leaves the matching semantics of query, category, transport, and limit unexplained, which an agent would need when composing a call.

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 only 33%, so four of six parameters (query, category, transport, limit) rely on the schema's bare types. The description indirectly clarifies live_only and max_tool_tokens by explaining that results report last-check status and token cost, but it never explains what query or category match against.

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?

States a specific verb and resource ('Find an MCP server') with two concrete examples (Stripe payments, browser automation). It also draws a boundary against web search, so an agent can separate it from stork_search without opening either schema.

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?

Gives explicit when-to-use ('when the user wants a tool installed') and an explicit when-not ('not for web search'). It does not name the sibling tools (stork_install, stork_search) that would handle those adjacent cases, leaving the routing slightly to inference.

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