TypeScript AST MCP Server

Overview Schema Source Related Servers Discussions Admin

get_callers

Find all functions in a file or package that call a specified function, revealing reverse call graphs for dependency analysis.

Instructions

Finds all functions in a file or package that call the specified function (reverse call graph)

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": {
      "path": "<path>",
      "function": "<function>"
    },
    "name": "get_callers"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes	Absolute path to the TS/JS file
`scope`	No	Analysis scope: 'file' or 'package'	file
`function`	Yes	Name of the target function (e.g., 'setup' or 'MyClass.method')

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 1, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are present, so the description must disclose behavioral context on its own. It mentions scope (file/package) and the reverse call graph concept, but omits details like whether callers are direct or transitive, the format of the result, and handling of unresolved symbols. 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 description is a single, front-loaded sentence that conveys the action, target, and scope with no redundant words. It is ideally concise.

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

Completeness2/5

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

With no output schema and no annotations, the description is too terse for a complex analysis tool. It fails to describe the return format, whether the search is direct or transitive, or how external function references are handled, leaving the tool under-specified for an agent.

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?

The input schema fully covers all three parameters (100% coverage) with descriptions for path, scope, and function. The description adds no substantive parameter details beyond restating the 'file or package' scope already in the schema, so the baseline 3 applies.

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 purpose with a specific verb ('Finds'), resource ('functions in a file or package that call the specified function'), and explicitly notes 'reverse call graph', distinguishing it from the sibling call_graph tool.

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

Usage Guidelines3/5

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

The description implies usage for reverse call analysis but does not explicitly reference alternatives or exclusion conditions. The term 'reverse call graph' hints at when to use it, but no direct comparison to siblings like call_graph or find_usages is provided.

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