Skip to main content
Glama
Sign In
gograph

gograph

by ozgurcd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

gograph_callees

Read-onlyIdempotent

Find functions and methods called by a specified Go function to map downstream dependencies. Returns callee symbols with package paths, file locations, and call-site line numbers, with optional depth expansion.

Instructions

Find functions and methods called by the specified function. Defaults to one-hop fan-out; depth 2-10 expands the downstream call graph. The MCP server refreshes source analysis before the call. Read-only; no persistent side effects. WHEN TO USE: To understand a function's downstream dependencies. NOT TO USE: For upstream callers (use gograph_callers); for package dependency trees (use gograph_deps). RETURNS: Callee 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)
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 name of the calling function to inspect callees for (supports short name 'Serve', dot-notation 'graph.Graph.Build', or 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. Changed2 schema fields changed
    • addedInput schema / properties / depth
      Added value: +{
+  "description": "Traversal depth from 1 to 10 (default 1)",
+  "type": "number"
+}
    • 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 calling function to inspect callees for (e.g., 'Serve', 'runMCP')"New value: +"The name of the calling function to inspect callees for (supports short name 'Serve', 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 calling function (e.g., 'InitServer')"New value: +"The name of the calling function to inspect callees for (e.g., 'Serve', 'runMCP')"
  9. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered; the description still adds a non-obvious behavior not in annotations, namely that the server refreshes source analysis before the call. It also discloses the depth-driven expansion and the mermaid output switch. It does not mention cost/latency of the refresh or pagination behavior under the limit/cursor pair, keeping it short of a 5.

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?

Four short, labeled segments (core behavior, WHEN TO USE, NOT TO USE, RETURNS) with the primary action and default fan-out front-loaded. No redundant restatement of the tool name and no filler sentences.

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?

There is no output schema, and the RETURNS section compensates by naming callee symbols, package paths, file locations, call-site line numbers, and the mermaid variant. Combined with the annotation-backed safety profile and the routing guidance, an agent has everything needed to select and invoke it correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter including root, cursor, session_id and intention is already documented in-schema; the baseline is 3. The description adds only marginal meaning beyond that — clarifying that depth 2-10 expands the graph and that mermaid=true swaps the response format for flowchart text. Useful framing but not compensating for any documented gap.

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 and resource ('Find functions and methods called by the specified function') and immediately pins the direction of traversal as downstream fan-out. It explicitly contrasts itself with gograph_callers (upstream) and gograph_deps (package trees), so an agent can discriminate it from siblings without opening any 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?

Provides an explicit WHEN TO USE ('understand a function's downstream dependencies') and a NOT TO USE clause naming the two alternative tools with the condition that selects each. This is the strongest form of routing guidance in the sibling set.

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