Skip to main content
Glama
Sign In
gograph

gograph

by ozgurcd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

gograph_impact

Read-onlyIdempotent

Find every symbol that transitively calls a target before refactoring, revealing the full upstream blast radius for a symbol, uncommitted changes, or a git ref.

Instructions

Traverse the call graph backwards to find every symbol that transitively calls the target — the full upstream blast radius of a change. The MCP server checks freshness before the call. Read-only; no side effects. Three modes: (1) single symbol via symbol; (2) uncommitted changes via uncommitted=true; (3) git-ref changes via since. WHEN TO USE: Before refactoring a core function to see what breaks. NOT TO USE: For direct one-hop callers only (use gograph_callers). RETURNS: Transitive upstream affected symbols; with mermaid=true, Mermaid flowchart text; a bounded native page (including empty pages). Exact and possible paths remain distinct; Mermaid uses dotted edges for possible evidence. Uncommitted modes compare declarations against HEAD, including selected untracked Go files. Traversal consumers refuse deleted declarations requiring historical caller evidence. Review instead includes changes --git HEAD declaration evidence and names unavailable historical callers, tests and risk. Incomplete comparisons and missing/ambiguous current identities remain errors. Rebuild before traversing newly added symbols.

Input Schema

NameRequiredDescriptionDefault
rootNoAbsolute path of the checkout you are working in (your cwd or git worktree). Must be this server's repository or one of its git worktrees; the answer then comes from that checkout's own graph. A path elsewhere is refused. Alias: cwd. Omit only when the configured checkout is the one you mean.
limitNoMaximum rows per page; the byte budget may return fewer.
sinceNoGit ref (e.g. 'main', 'HEAD~5'): blast radius of all symbols changed since this ref
cursorNoOpaque next_cursor for the same graph snapshot and result selection.
symbolNoSymbol name for single-symbol blast radius (supports short name 'ValidateToken', dot-notation 'graph.Graph', or fully-qualified ID)
mermaidNoReturn Mermaid flowchart text instead of the normal response
intentionNoTechnical rationale, required for analytical calls selecting an active session.
exact_onlyNoExclude any path that depends on possible call evidence; default false retains explicitly labeled possible results
session_idNoCaller selector returned by session_create. Omission means an independent caller; never inherits server environment or another caller's session.
uncommittedNoIf true, compute blast radius of all uncommitted modified symbols

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.7.18
    • addedInput schema / properties / intention
      Added value: +{
+  "description": "Technical rationale, required for analytical calls selecting an active session.",
+  "type": "string"
+}
    • addedInput schema / properties / root
      Added value: +{
+  "description": "Absolute path of the checkout you are working in (your cwd or git worktree). Must be this server's repository or one of its git worktrees; the answer then comes from that checkout's own graph. A path elsewhere is refused. Alias: cwd. Omit only when the configured checkout is the one you mean.",
+  "type": "string"
+}
    • addedInput schema / properties / session_id
      Added value: +{
+  "description": "Caller selector returned by session_create. Omission means an independent caller; never inherits server environment or another caller's session.",
+  "type": "string"
+}
  2. Changed3 schema fields changedv1.7.5
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Opaque next_cursor for the same graph snapshot and result selection.",
+  "maxLength": 128,
+  "type": "string"
+}
    • addedInput schema / properties / exact_only
      Added value: +{
+  "description": "Exclude any path that depends on possible call evidence; default false retains explicitly labeled possible results",
+  "type": "boolean"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 100,
+  "description": "Maximum rows per page; the byte budget may return fewer.",
+  "maximum": 200,
+  "minimum": 1,
+  "type": "integer"
+}
  3. Changed1 schema field changedv1.5.6
    • addedInput schema / properties / mermaid
      Added value: +{
+  "description": "Return Mermaid flowchart text instead of the normal response",
+  "type": "boolean"
+}
  4. Addedv1.5.3
  5. Removedv1.5.3
  6. Changed1 schema field changed
    • changedInput schema / properties / symbol / description
      Previous value: -"Symbol name for single-symbol blast radius (e.g., 'ValidateToken')"New value: +"Symbol name for single-symbol blast radius (supports short name 'ValidateToken', dot-notation 'graph.Graph', or fully-qualified ID)"
  7. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description still adds real value: a freshness check before the call, the exact-vs-possible evidence distinction with dotted Mermaid edges, comparison against HEAD including selected untracked Go files, refusal of deleted declarations, and the instruction to rebuild before traversing new symbols. The middle section is muddied by a garbled sentence beginning 'Review instead includes changes --git HEAD declaration evidence', which reads as leakage about a sibling tool and weakens otherwise strong disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The structure is strong and front-loaded — purpose, freshness, modes, when/when-not, returns, edge cases — and every early sentence earns its place. However the final third becomes a dense run-on of edge-case rules ('Traversal consumers refuse deleted declarations requiring historical caller evidence...') plus the garbled 'Review instead includes' sentence, which costs the reader more than it returns.

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 10-parameter, zero-required tool with no output schema, the description covers the essentials: what comes back (transitive upstream symbols, a bounded native page including empty pages, Mermaid text), error conditions for incomplete comparisons and missing identities, and the freshness prerequisite. The only real gap is that session/intention parameters, which gate analytical calls, are left entirely to the schema.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds semantics the schema cannot express: the three modes are mutually exclusive entry points mapped to `symbol`, `uncommitted`, and `since`, and it clarifies that mermaid swaps the response shape entirely. It does not add anything for root, limit, cursor, session_id, or intention beyond what the schema already documents.

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

Purpose5/5

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

The opening sentence gives a specific verb and resource — 'Traverse the call graph backwards to find every symbol that transitively calls the target' — and immediately frames it as 'the full upstream blast radius of a change'. It explicitly distinguishes itself from the sibling gograph_callers by scoping that tool to 'direct one-hop callers only', so an agent can route correctly without opening either schema.

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

Usage Guidelines5/5

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

Dedicated 'WHEN TO USE' and 'NOT TO USE' blocks name both the triggering situation (before refactoring a core function) and the alternative tool (gograph_callers) with the condition that selects it. The three invocation modes (symbol, uncommitted=true, since) are enumerated, which covers the main decision points an agent faces.

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

Deploy Server

Other Tools