TypeScript AST MCP Server

Overview Schema Source Related Servers Discussions Admin

find_errors

Detects TypeScript error patterns including floating promises, empty catches, unsafe assertions, and double assertions to help identify potential issues.

Instructions

Analyzes TypeScript-specific error patterns: floating promises, empty catches, unsafe type assertions, double assertions

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

Input Schema

Name	Required	Description	Default
`path`	Yes	Absolute path to the TS/JS file
`function`	No	Scope analysis to a specific function

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 1, 2026

TDQS

A3.6/5.0

Behavior2/5

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

The description only lists the patterns analyzed but does not disclose what the tool returns, whether it modifies anything, or any prerequisites. With no annotations available, this leaves important behavioral aspects unstated.

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?

A single, focused sentence front-loads the key purpose and lists concrete error patterns; no wasted words.

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?

Without an output schema, the description should explain the return value or result format, but it only mentions the analysis scope. The lack of behavioral context (e.g., read-only, output shape) makes it incomplete for an agent to fully anticipate the tool's response.

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 fully describes both parameters (path and function) with 100% coverage, so the description adds no additional parameter meaning. Baseline score of 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 'Analyzes' and a specific resource 'TypeScript-specific error patterns' with concrete examples (floating promises, empty catches, etc.), clearly distinguishing it from sibling tools like code_smells or dead_code.

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

Usage Guidelines4/5

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

It gives clear context by specifying TypeScript-specific patterns, implying it's for TS files, but it does not explicitly compare with alternatives or explain when to prefer it over tools like code_smells.

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