Skip to main content
Glama

Find an MCP server

stork_find_server
Read-only

Find MCP servers for a task or product and compare matches by connection details, endpoint availability, tool-token cost, and observed test-call results.

Instructions

Find MCP servers for a task or product (for example: Stripe payments, browser automation). Returns matching servers from Stork's directory, each with how to connect, whether its endpoint answered Stork's last check, how many tokens its tool definitions take, and what Stork's own test calls saw.

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 observedv1.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish a safe, open-world read, so the description focuses on adding value — it discloses that results come from Stork's directory, carry connection info, reflect the last endpoint check, and include token costs and observed test-call results. That is meaningful disclosure beyond the annotations, though the freshness window of "last check" is not quantified.

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 tool's function is front-loaded in the first clause, followed by a compact enumeration of what each result contains. Two sentences, no filler; only the long result enumeration could have been tightened.

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 six parameters, no output schema, and low schema coverage, the description does well on the return-value side but is thin on input semantics. An agent still has to guess at valid categories, how filters interact, and how limit affects the result set.

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 the description has to carry weight. It implicitly explains live_only ("whether its endpoint answered Stork's last check") and max_tool_tokens ("how many tokens its tool definitions take"), but says nothing about limit, category, or transport, leaving half the parameters defined only by their names.

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 and resource ("Find MCP servers") plus the scoping input ("for a task or product") and gives two concrete query examples. The purpose is unambiguous, though it never contrasts itself with siblings like stork_search or stork_repo, so differentiation is left to the agent.

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?

The example queries (Stripe payments, browser automation) imply the discovery use case, but there is no explicit when-to-use guidance, no mention of when a different Stork tool is the better choice, and no note on combining filters. Usage is inferable rather than stated.

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