Skip to main content
Glama

weavegraph_index_repo

Index a repository's AST dependency graph, find cycles via Tarjan SCC, and compute topological build waves for dependency-aware task planning.

Instructions

Index a repository AST dependency graph, Tarjan SCC cycles, and topological build waves.

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_path": "<repo_path>"
    },
    "name": "weavegraph_index_repo"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_filesNo
repo_pathYesAbsolute or relative repository directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden, yet it does not say whether indexing is read-only or persists anything to disk, whether it is idempotent or cached, how long it takes on large repos, or what the default 500-file cap does when exceeded. "Index" is a suggestive but undefined term for side effects.

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?

A single front-loaded sentence with no filler; the pipeline stages are ordered as they execute. Nothing in it needs removing.

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 and no annotations, the description should say what the index call returns or produces, since an agent cannot otherwise know how to interpret the result. It is adequate as a one-line summary of a simple two-parameter tool but leaves the output side entirely implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only repo_path is documented in the schema (50% coverage); max_files has a default of 500 but no stated meaning in either schema or description. The description never mentions that max_files exists, so an agent cannot know whether it truncates, errors, or is a performance guard.

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 names a specific verb and resource ("Index a repository AST dependency graph") and enumerates the computed artifacts: Tarjan SCC cycles and topological build waves. An agent can tell this is a graph-analysis/indexing operation, distinct from the sibling tools (blast radius, worktree planning, merge verification), though the description never explicitly contrasts itself with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use, when-not-to-use, or prerequisite guidance. It is only implicit that this is a foundational step whose output feeds the other weavegraph_* tools; nothing states whether it must be run first or how often it can be re-run.

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