Skip to main content
Glama

repo_graph

Read-onlyIdempotent

Export indexed codebase nodes and relationships to analyze dependencies and reuse repository structure in external tools.

Instructions

Export the indexed nodes and relationships.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "repo_graph"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.6

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description. The description adds only the subject of the export and leaves the behaviorally important question unresolved: whether "export" returns the graph in the response or produces an artifact somewhere, and what volume/format to expect.

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?

A single short sentence with no filler, and the key noun (indexed nodes and relationships) is stated immediately. It is efficient, though the brevity edges into under-specification rather than tightness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters, no output schema, and no annotations about return content, the description is the only place a caller can learn what comes back from an "export." It does not state the format, the scope of the graph (whole repo vs. filtered), whether the result is paginated or truncated, or the shape of nodes/edges, so an agent cannot predict the response.

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

Parameters4/5

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

The tool takes zero parameters and the schema has no properties, so there is no parameter meaning for the description to add. The baseline of 4 applies; the description neither helps nor misleads on inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Export the indexed nodes and relationships" supplies a verb (Export) and a resource (indexed nodes and relationships), so the subject matter is identifiable. However, "export" is ambiguous — it could mean returning data to the caller or writing a file — and nothing distinguishes this from graph-shaped siblings like repo_architecture or repo_dependencies.

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 guidance at all: no mention of when an agent should call repo_graph rather than repo_architecture, repo_dependencies, or repo_search. The agent must guess from the name alone, and the description never names an alternative or a triggering condition.

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