Skip to main content
Glama
Sign In
codegraph-mcp

codegraph-mcp

by SiwarKhalfaoui
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Find what a symbol calls

find_callees

Retrieve every function and method invoked inside a given symbol to understand its dependencies.

Instructions

Find every function/method called from within a given symbol.

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_id": "<symbol_id>"
    },
    "name": "find_callees"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbol_idYesExact symbol id from find_definition
graph_pathNoPath to a previously saved graph (default: .codegraph/graph.json)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states what the tool finds but not whether the search is direct or transitive, what the output format is, or whether it reads from the graph without modification. This leaves significant ambiguity.

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?

The entire description is a single, focused sentence with no unnecessary words. It is appropriately front-loaded and easily parseable by an agent.

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

Completeness3/5

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

Given no output schema, the description should at least hint at the return structure. It does not. Although the params are well-documented, the tool lacks a full behavioral contract, making it adequate but not complete.

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 coverage is 100%, with each parameter having a description, including the requirement that symbol_id is an exact symbol id from find_definition. The description adds no additional parameter information, so the schema itself does the heavy lifting.

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 description clearly states the tool's function (find callees) with a specific verb and resource. It distinguishes from siblings like find_callers, which would be the inverse operation. The phrasing 'from within a given symbol' directly conveys the scope.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives like find_callers or get_file_dependencies. The description does not mention that symbol_id should come from find_definition, although the schema does. No exclusions or comparisons provided.

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