Skip to main content
Glama

Stork MCP Directory

stork_server_details

Read-onlyIdempotent

Get full details about a specific MCP server, including check (what Stork's last request to its endpoint saw, with the estimated token size of its tool definitions) and toolChanges (each time a check found different tool definitions than the check before, and whether the server's version changed with them).

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": {
      "slug": "<slug>"
    },
    "name": "stork_server_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety semantics are covered. The description does add real value by explaining what the two named result sections mean (`check` = last observed endpoint state with estimated token size of tool definitions; `toolChanges` = diffs across checks with version-change flag). It stops short of describing the rest of the payload or what happens for a nonexistent server.

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 sentence that front-loads the core action before unpacking the two highlighted return sections. The nested parentheticals are dense but each clause carries information; nothing is redundant.

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 carries the burden of describing the response, and it only explains two of the returned sections while leaving the remaining detail fields unspecified. For a one-parameter read tool with annotations covering safety, this is adequate but not complete.

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?

Only one parameter (`slug`) exists and the schema gives it zero description coverage, so the description must compensate. Saying it returns details 'about a specific MCP server' implies the slug is a server identifier, but it adds no format, casing, or source-of-slug guidance.

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 ('Get full details about a specific MCP server') and enumerates the notable returned sections (`check`, `toolChanges`), so the agent knows this is a per-server detail lookup rather than a search. It does not explicitly distinguish itself from siblings like stork_search or stork_compare, leaving that inference 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?

Usage is only implied: needing one specific server's full record selects this tool, and the mention of a 'specific' server hints at the slug-keyed lookup versus a search. No when-not conditions, prerequisites, or named alternatives are given, and there is no guidance on behavior when the slug is unknown.

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