Skip to main content
Glama

Stork MCP Directory

stork_compare

Read-onlyIdempotent

Compare 2 to 5 MCP servers side by side by slug: how each connects, licence, tool list, and what Stork's last check of each endpoint 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": {
      "slugs": "<slugs>"
    },
    "name": "stork_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description goes further by naming what comes back — how each connects, licence, tool list, and 'what Stork's last check of each endpoint saw' — which is genuinely additive given there is no output schema. It does not explain what a 'last check' result looks like or how stale/failed checks are represented.

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?

One sentence, front-loaded with the verb and resource, with the enumerated outputs folded into a compact colon list. No redundant restatement of the tool name and nothing that could be trimmed without losing information.

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 single-parameter read-only tool with annotations present and no output schema, the description covers purpose, input meaning, and the shape of the returned data. The remaining gaps — handling of invalid slugs or servers with missing check data — are minor rather than blocking.

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

Parameters4/5

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

Schema description coverage is 0% and the single required parameter is only typed as an array of strings, so the description must carry the meaning — and it does, clarifying that the values are server slugs and that 2 to 5 must be supplied. It does not add slug formatting, ordering, or duplicate-slug behaviour.

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 uses a specific verb and resource ('Compare ... MCP servers') and pins the scope precisely ('2 to 5 ... by slug'), then enumerates the comparison axes: connection method, licence, tool list, and last endpoint check. That reads as unmistakably different from a single-server tool such as stork_server_details without needing to open 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'side by side' and the 2–5 range imply the tool is for multi-server comparison rather than inspecting one server, which gives an agent a usable usage signal. However, no alternative is named and there is no explicit when-not guidance, so the routing decision is left partly 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