Skip to main content
Glama
ozgurcd

gograph

by ozgurcd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

gograph_impact

Read-onlyIdempotent

Find every symbol that transitively calls a target to see the full upstream blast radius of a code change before refactoring.

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. Current-graph consumers refuse incomplete comparisons, deleted declarations requiring historical caller evidence, and missing/ambiguous graph identities. Inspect changes --git REF for the declaration census; rebuild before traversing newly added symbols.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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
exact_onlyNoExclude any path that depends on possible call evidence; default false retains explicitly labeled possible results
uncommittedNoIf true, compute blast radius of all uncommitted modified symbols

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. Changed1 schema field changedv1.5.6
    • addedInput schema / properties / mermaid
      Added value: +{
+  "description": "Return Mermaid flowchart text instead of the normal response",
+  "type": "boolean"
+}
  3. Addedv1.5.3
  4. Removedv1.5.3
  5. 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)"
  6. First observedv1.0.0

TDQS

A4.6/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), so 'Read-only; no side effects' is partly redundant. However the description adds substantial beyond-annotation behavior: a pre-call freshness check, refusal conditions for incomplete comparisons/deleted declarations/ambiguous identities, and the requirement to rebuild before traversing newly added symbols.

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?

Front-loaded with the core purpose, then modes, usage guidance, returns, and constraints in a scannable order. It is dense and slightly long, but nearly every sentence carries actionable detail rather than filler.

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

Completeness5/5

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

With no output schema, the description carries the return-value burden well: it lists the transitive upstream symbols, Mermaid flowchart text, bounded paging including empty pages, and the exact/possible distinction. Modes, constraints, and edge cases are all covered, leaving nothing an agent needs to call it correctly.

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 real meaning by framing the three mutually exclusive modes (symbol, uncommitted, since) and clarifying exact_only semantics (excludes paths relying on possible evidence) and mermaid output. It goes beyond the per-field schema text.

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?

States a specific verb (traverse backwards), resource (call graph / symbols), and scope (full upstream blast radius), which immediately distinguishes it from the one-hop sibling gograph_callers. An agent can tell exactly what it computes without opening the 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?

Has explicit WHEN TO USE ('before refactoring a core function to see what breaks') and NOT TO USE ('for direct one-hop callers only, use gograph_callers') guidance. The alternative and the condition that selects it are both named.

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