Skip to main content
Glama

Stork: search, scrape and docs

stork_install

Read-only

Set up an MCP server for the user: say what they want connected (Notion, Supabase, Sentry, Postgres, a browser) and their client, and get the config to write, what the user must supply (a sign-in or keys), and who publishes the server. Stork picks the vendor's own server where there is one. Use this when the tool needs the user's own account, which Stork cannot use for them. Show the user who publishes the server before writing the config.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe product or job, for example Notion, Supabase, browser automation.
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.9/5.0
Behavior4/5

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

With readOnlyHint and openWorldHint already supplied, the description adds real context: it returns config rather than writing it, it reports which credentials the user must provide, and it surfaces the publisher for a trust check. This confirms the read-only nature ("get the config to write") instead of contradicting it, though it doesn't mention failure modes when no vendor server exists.

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 purpose and deliverables are front-loaded in the first sentence, with selection criteria and the trust-check instruction following in logical order. The dense enumeration of examples and outputs makes it slightly packed, but no sentence is wasted.

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 fills the gap by naming what comes back: config, required credentials, and publisher. For a two-parameter tool with full schema coverage, this covers what an agent needs to call it and relay results, though the behavior when a vendor server doesn't exist is left implicit.

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 100%, and both parameters already carry descriptions, so the schema does the heavy lifting. The description reinforces which inputs to gather (product and client) and broadens the example set beyond the schema, but adds no format or validation detail beyond what is already structured.

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 description opens with a specific verb and resource ("Set up an MCP server for the user") and enumerates the deliverables: config to write, credentials the user must supply, and the server's publisher. It does not name a sibling explicitly, so differentiation from stork_find_server is only implied through "Stork picks the vendor's own server where there is one."

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?

It gives a clear selection condition: "Use this when the tool needs the user's own account, which Stork cannot use for them." It also adds a usage instruction (show the publisher before writing config) but never names an alternative tool to use when the user's account isn't needed.

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