TypeScript AST MCP Server

Overview Schema Source Related Servers Discussions Admin

get_doc

Retrieve JSDoc/TSDoc comments for any TypeScript symbol, including methods via Class.method syntax, to understand code without reading source.

Instructions

Extracts JSDoc/TSDoc comments for a symbol (function, type, class, variable). Supports Class.method syntax.

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

Input Schema

Name	Required	Description	Default
`name`	Yes	Symbol name (e.g., 'Config', 'MyClass.method', 'DEFAULT_VALUE')
`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.7/5.0

Behavior3/5

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

With no annotations, the description must carry the full burden of behavioral disclosure. It states the core behavior (extracts comments) and the supported syntax, but does not explain what happens if no doc comment exists, whether it returns the raw comment, or any error behavior. This leaves moderate ambiguity for a simple read-only tool.

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 extremely concise, consisting of two short sentences that front-load the primary action. Every word adds value, with no fluff or redundancy.

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?

The tool is simple with two parameters and no output schema, but the description does not detail the return format or behavior in edge cases (e.g., missing comments, invalid symbol). Given the lack of output schema, this gap in completeness makes the description minimally adequate but not fully comprehensive.

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 schema already provides 100% coverage with descriptive examples for both parameters. The description adds the list of symbol types (function, type, class, variable), but this overlaps with the schema's example values, providing minimal additional meaning beyond the schema.

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 extracts JSDoc/TSDoc comments for a symbol, listing the symbol types (function, type, class, variable) and noting support for Class.method syntax. This specific verb+resource combination clearly distinguishes it from sibling tools like get_type_definition or get_function_body.

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 the tool is used when documentation comments are needed, but it does not explicitly state when to use it over alternatives or when not to use it. There are no references to other tools or context-based guidance, so usage is implied rather than clearly directed.

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