Skip to main content
Glama

Stork MCP Directory

stork_get_install_config

Read-onlyIdempotent

Ready-to-paste client config for one MCP server. Check installKnown first: when it is false, config is null because Stork holds no verified install method, and instructions links the publisher's own setup guide. Do not invent a command in that case. installMethod is 'remote' (connect by URL) or 'npm' (local stdio). authSummary says when the user must sign in.

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

Input Schema

NameRequiredDescriptionDefault
slugYes
clientNoThe user's MCP client: cursor, claude-desktop, claude-code, vscode, zed. Any other name gets the common mcpServers JSON.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this read-only, idempotent and open-world, so the safety profile is covered. The description adds real value on top: the null-config edge case, the reason for it, the fact that instructions points to the publisher's guide, the meaning of installMethod values, and what authSummary tells the user.

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?

Four tight sentences, front-loaded with what the tool returns, then the failure case and the field glossary. Every sentence carries information, though the mix of bare field names and backticked ones is slightly uneven.

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?

With no output schema, the description usefully explains the key returned fields (config, installKnown, instructions, installMethod, authSummary) and the null case, which is what an agent needs to act on the result. The only gap is the meaning of the required slug parameter.

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 description coverage is 50% — the client parameter is fully documented in the schema while slug is not — so the baseline sits at 3. The phrase 'for one MCP server' hints that slug identifies the target, but the description never explains slug's format or how client gaps fall back to the common mcpServers JSON, which is described only in the schema.

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 first sentence pins down a concrete artifact: a ready-to-paste client config for one MCP server. That is specific enough to separate it from stork_server_details or stork_search, which would be about metadata rather than connection config, though the description never names a sibling explicitly.

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 a clear conditional workflow — check installKnown first, and when it is false do not invent a command because config is null — which is genuinely useful usage guidance. However, it never states when to reach for this tool rather than stork_server_details, so the selection guidance is implied rather than explicit.

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