TypeScript AST MCP Server

Overview Schema Source Related Servers Discussions Admin

call_graph

Generate a Mermaid flowchart showing function call dependencies in TypeScript/JavaScript code, with options to scope to a file or package, start from a specific function, and include external calls.

Instructions

Generates a Mermaid flowchart showing the call graph of functions in a TypeScript/JavaScript file or directory

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>"
    },
    "name": "call_graph"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes	Absolute path to the TS/JS file
`scope`	No	Analysis scope: 'file' or 'package'	file
`function`	No	Focus on calls reachable from this function only
`direction`	No	Graph direction: TD (top-down) or LR (left-right)	TD
`include_external`	No	Include calls to external functions

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 1, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description carries full responsibility for behavioral disclosure. It merely says it generates a flowchart, with no mention of read-only nature, performance implications, output format details, or how external calls are handled beyond the include_external parameter.

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 directly states the tool's purpose. No filler or redundancy; every word earns its place.

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?

Despite having 5 parameters and two enums, the description offers no detail about the output format, return behavior, or limitations. It lacks information on how the Mermaid flowchart is returned (string? file?) and does not differentiate from similar sibling tools, making it incomplete for reliable invocation.

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

Parameters2/5

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

Schema coverage is 100%, so the schema already documents parameters well. However, the description introduces ambiguity by saying 'file or directory' while the path parameter schema says 'file', potentially misleading an agent about accepted inputs. No additional parameter semantics are clarified.

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 states a specific verb ('Generates') and resource ('Mermaid flowchart showing the call graph of functions'), clearly distinguishing it from sibling analysis tools. The scope ('TypeScript/JavaScript file or directory') adds useful context.

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 guidance is provided on when to use this tool versus alternatives like get_callers or find_usages. The description only states what it does, not when it's the preferred choice or when to avoid it.

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