Skip to main content
Glama

Ask about a GitHub repository

stork_repo
Read-only

Answers questions about code in public GitHub repositories, explaining how features are implemented, where code lives, and how it is used via indexed repository data.

Instructions

Answer a question about the code in a public GitHub repository: how something is implemented, where it lives, how it is used. The answer comes from DeepWiki, which has indexed the repository, and is named in the reply's via field. Can take 10 to 20 seconds.

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": {
      "repo": "<repo>",
      "question": "<question>"
    },
    "name": "stork_repo"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesowner/name, for example vercel/next.js, or the repository's GitHub address.
questionYesWhat you want to know about the code.
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.5/5.0
Behavior3/5

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

Beyond the readOnly/openWorld annotations, the description usefully discloses the answer source (DeepWiki's index) and that it is attributed in the reply's `via` field. However, it leaves the 10-20 second figure unexplained (is that a hard timeout? do retries help?) and never says what happens when a question is unanswerable.

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?

Three tight sentences: what it does, where the answer comes from, then the latency caveat last. Every sentence carries information, and the latency warning is placed where a reader will still see it without it crowding the opening.

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 two-required-parameter read tool with no output schema this is largely sufficient: it covers the resource, the answer provenance, the attribution field, and the expected wait. The main residual gap is failure behavior for unanswerable questions or repos not indexed by DeepWiki.

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 repo format, question meaning, and the token cap are already documented in the schema. The description adds nothing to the parameters themselves, so the baseline of 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?

The description gives a specific verb and resource: answer a question about code in a public GitHub repository, with examples of the question types (how implemented, where it lives, how used). It implicitly separates itself from the docs/scrape/search siblings by scoping to indexed public repo code Q&A, though it never names an alternative 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 'public GitHub repository' and by the 10-20 second latency warning, which helps an agent decide whether to wait. There is no explicit when-not-to-use, no mention of private repos being out of scope, and no routing to stork_search or stork_docs as alternatives.

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