Skip to main content
Glama

krusch_git_dependency_graph

Read-onlyIdempotent

Trace inbound callers and outbound callees for a symbol to see what breaks before changing a signature.

Instructions

Trace inbound callers and outbound callees for a symbol before modifying signatures.

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

Input Schema

NameRequiredDescriptionDefault
repoNo
symbolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the description carries a lighter burden. What it adds is workflow intent rather than behavior: it never says whether the trace is direct callers only or transitive, how deep the graph goes, or what language/AST assumptions apply. Useful but thin given the analysis complexity.

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 sentence with the action front-loaded and the motivating use case trailing; nothing is redundant or padded. Every clause contributes.

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 output schema and zero schema description coverage, the description is the only source of detail for a tool whose return value is a call graph. It leaves the `repo` parameter unexplained and gives no sense of result shape or size, which is too little for a graph-tracing tool with an undocumented result.

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?

Schema description coverage is 0%, so the description must compensate and it largely does not. "for a symbol" gestures at the required `symbol` parameter but gives no expected format (fully qualified name? file:line?), and the `repo` parameter is never mentioned at all, leaving the agent to guess whether it defaults to a current repo.

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?

"Trace inbound callers and outbound callees for a symbol" states a specific verb (trace) plus the two resources it returns, which cleanly separates it from search/lookup siblings like krusch_git_search_symbols or krusch_git_file_symbols. It stops short of naming any sibling explicitly, so the differentiation is inferred rather than declared.

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?

"before modifying signatures" supplies a concrete triggering condition that tells the agent when this tool earns its cost. There is no when-not guidance and no named alternative for shallower symbol lookups, which keeps it below a 5.

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