TypeScript AST MCP Server

Overview Schema Source Related Servers Discussions Admin

dead_code

Find unreferenced functions, types, and variables in TypeScript/JavaScript code to expose dead code and simplify refactoring.

Instructions

Finds unreferenced unexported symbols (functions, types, variables) within a 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": "dead_code"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes	Absolute path to the directory
`include_tests`	No	Include test files (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 1, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that it finds only unexported unreferenced symbols within a directory, adding some behavioral context. However, it does not explain how 'unreferenced' is determined, whether cross-package references are considered, or what the return format looks like.

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 clearly states the action and scope without extraneous information. Every word earns its place.

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

Completeness4/5

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

For a simple read-only analysis tool with two fully documented parameters, the description covers the core function and scope adequately. Although there is no output schema or return format explained, the nature of the tool makes the result (a list of dead symbols) reasonably implicit. Slightly more detail on the definition of 'unreferenced' would make it fully 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 both 'path' and 'include_tests' fully described. The tool description adds no additional parameter semantics beyond what the schema provides, so baseline 3 is appropriate.

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 'Finds unreferenced unexported symbols (functions, types, variables) within a directory' uses a specific verb and resource, clearly stating the tool's scope. It distinguishes itself from siblings like list_declarations or find_usages by focusing on unreferenced, unexported symbols.

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 dead code detection within a directory but does not provide explicit when-to-use/when-not-to-use guidance or name alternative tools. There is no exclusionary context, so the usage is only implied.

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