TypeScript AST MCP Server

Overview Schema Source Related Servers Discussions Admin

list_imports

Get a complete list of import statements from a TypeScript/JavaScript file, including each imported binding and the module path.

Instructions

Lists all import statements in a TypeScript/JavaScript file with their bindings and module paths

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": "list_imports"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes	Absolute path to the TS/JS file

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 states a read-only action ('Lists') and describes the output contents, but does not disclose potential limitations, error behavior, or return structure beyond the bindings and module paths. For a simple list operation, this is adequate but not rich.

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 with no filler. It directly communicates the tool's function and scope.

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 tool with one parameter and no output schema, the description adequately explains what the tool returns (bindings and module paths). It might be improved by specifying whether imports are sorted or filtered, but the core information is present and sufficiently complete for the tool's simplicity.

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 the only parameter 'path' described as 'Absolute path to the TS/JS file'. The description adds little beyond this, mainly reaffirming the file type. With full schema coverage, 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 uses a specific verb ('Lists') and clearly identifies the resource ('all import statements in a TypeScript/JavaScript file') plus the detail 'with their bindings and module paths'. This distinguishes it from siblings like list_exports and list_functions.

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 when to use the tool (when you need to inspect imports) but does not explicitly mention alternatives or when not to use it. Given the large set of sibling tools, explicit guidance would help, but the purpose is clear enough for basic inference.

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