Skip to main content
Glama
Sign In
gograph

gograph

by ozgurcd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

gograph_callers

Read-onlyIdempotent

Find functions and methods that call a target Go function or interface method, including callers-of-callers, to assess fan-in before renaming, removing, or changing its signature.

Instructions

Find functions and methods that call the specified function or interface method. Defaults to one-hop fan-in; depth 2-10 expands callers-of-callers. In a precise graph, Interface.Method expands through all recorded implementations and reports a shared source call site once. The MCP server refreshes source analysis before the call. Read-only; no persistent side effects. WHEN TO USE: Before renaming, removing, or changing a function or interface method signature. NOT TO USE: For unbounded upstream blast radius (use gograph_impact); for downstream callees (use gograph_callees). RETURNS: Caller symbols with package paths, file locations, and call-site line numbers; with mermaid=true, Mermaid flowchart text.

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.
depthNoTraversal depth from 1 to 10 (default 1)
exactNoRequire an exact symbol-name or fully-qualified-ID match
limitNoMaximum rows per page; the byte budget may return fewer.
cursorNoOpaque next_cursor for the same graph snapshot and result selection.
mermaidNoReturn Mermaid flowchart text instead of the normal response
functionYesThe target function or method (supports short name 'BuildGraph', interface notation 'Repository.Delete', concrete dot-notation 'Store.Delete', or a fully-qualified ID)
no_testsNoExclude call edges originating in *_test.go files
intentionNoTechnical rationale, required for analytical calls selecting an active session.
session_idNoCaller selector returned by session_create. Omission means an independent caller; never inherits server environment or another caller's session.

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. Changed2 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 / limit
      Added value: +{
+  "default": 100,
+  "description": "Maximum rows per page; the byte budget may return fewer.",
+  "maximum": 200,
+  "minimum": 1,
+  "type": "integer"
+}
  3. Changed2 schema fields changedv1.5.6
    • changedInput schema / properties / depth / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / mermaid
      Added value: +{
+  "description": "Return Mermaid flowchart text instead of the normal response",
+  "type": "boolean"
+}
  4. Addedv1.5.4
  5. Removedv1.5.3
  6. Changed4 schema fields changed
    • addedInput schema / properties / depth
      Added value: +{
+  "description": "Traversal depth from 1 to 10 (default 1)",
+  "type": "number"
+}
    • addedInput schema / properties / exact
      Added value: +{
+  "description": "Require an exact symbol-name or fully-qualified-ID match",
+  "type": "boolean"
+}
    • changedInput schema / properties / function / description
      Previous value: -"The name of the target function to find callers for (supports short name 'BuildGraph', dot-notation 'graph.Graph.Build', or fully-qualified ID)"New value: +"The target function or method (supports short name 'BuildGraph', interface notation 'Repository.Delete', concrete dot-notation 'Store.Delete', or a fully-qualified ID)"
    • addedInput schema / properties / no_tests
      Added value: +{
+  "description": "Exclude call edges originating in *_test.go files",
+  "type": "boolean"
+}
  7. Changed1 schema field changed
    • changedInput schema / properties / function / description
      Previous value: -"The name of the target function to find callers for (e.g., 'BuildGraph', 'Serve')"New value: +"The name of the target function to find callers for (supports short name 'BuildGraph', dot-notation 'graph.Graph.Build', or fully-qualified ID)"
  8. Changed1 schema field changedv1.4.70
    • changedInput schema / properties / function / description
      Previous value: -"The name of the function being called (e.g., 'ValidateToken')"New value: +"The name of the target function to find callers for (e.g., 'BuildGraph', 'Serve')"
  9. First observedv1.0.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, and non-destructive behavior, yet the description adds real context: default one-hop fan-in, depth 2-10 semantics, interface dispatch expansion through all recorded implementations with a shared source call site reported once, and a pre-call source-analysis refresh. These are behavioral facts not recoverable from structured fields.

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?

Front-loaded with purpose and default scope, then clearly demarcated WHEN TO USE, NOT TO USE, and RETURNS segments. Every sentence carries information; nothing is redundant with the schema or annotations.

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?

For a 10-parameter analysis tool with no output schema, the description covers the return shape (caller symbols, package paths, file locations, call-site line numbers, Mermaid alternative), the default depth, and the interface-expansion edge case. The remaining parameters are fully documented in the schema, so nothing an agent needs is missing.

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 3 is the baseline, and the description earns a bump by explaining what depth actually does (2-10 expands callers-of-callers vs. the default one-hop) and that mermaid switches the response to flowchart text. It does not add meaning for root, cursor, limit, no_tests, or session parameters beyond the schema.

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: 'Find functions and methods that call the specified function or interface method.' It immediately distinguishes itself from the sibling gograph_callees (which returns the opposite direction) and from gograph_impact (which handles broader blast radius).

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?

Explicit WHEN TO USE (before renaming, removing, or changing a signature) and NOT TO USE clauses naming both alternatives with the condition that selects them (unbounded upstream blast radius → gograph_impact; downstream callees → gograph_callees). Nothing is left to inference.

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