Skip to main content
Glama

Look up library documentation

stork_docs
Read-only

Look up current documentation for a code library or framework and return the passages and code examples that answer your question, including vendor-hosted docs.

Instructions

Look up current documentation for a code library or framework. Returns the passages and code examples that fit a question. The lookup is run by a documentation provider (Context7, or the vendor's own documentation server for Microsoft, AWS and Cloudflare), which is named in the reply's via field.

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": {
      "library": "<library>",
      "question": "<question>"
    },
    "name": "stork_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
libraryYesLibrary or framework name, for example next.js, convex, stripe.
questionYesWhat you need to know about it.
max_result_tokensNoCap on the size of the reply. Default 3000, at most 6000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld, so the bar is lower; the description still adds real value by disclosing that the lookup is executed by an external documentation provider and that provenance appears in the reply's `via` field. It omits failure modes, rate limits, and what happens when a library is unknown.

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?

Three tight sentences: purpose first, return shape second, provenance third. No filler and nothing buried.

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?

No output schema exists, and the description compensates by describing the return shape and the `via` provenance field. For a three-parameter read-only lookup this is essentially complete, though error/empty-result behavior is unstated.

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%, so `library`, `question`, and `max_result_tokens` are already documented with examples and a default. The description adds nothing about parameter interpretation, so the baseline 3 applies.

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 ("Look up current documentation for a code library or framework") plus the shape of the return (passages and code examples). It is clearly distinct from scrape/search-style siblings, but it never names or contrasts any of them 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?

Usage is implied by phrasing ("the passages and code examples that fit a question"), so an agent can infer this is for answering doc questions. There is no explicit when-not-to-use guidance and no routing advice versus stork_search or stork_scrape.

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