ts-mcp-server

Overview Schema Source Related Servers Discussions Admin

Get Code Fixes

getCodeFixes

Read-only

Retrieve available code fixes for specific error codes at a defined range in a TypeScript or JavaScript file. Uses diagnostic error codes and range to return tsserver's suggested code actions.

Instructions

Get available code fixes for specific error codes at a range in a TypeScript/JavaScript file. Returns the raw list of code actions tsserver suggests for the given diagnostics. Use getDiagnostics first to discover error codes and ranges, then pass them here.

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": {
      "file": "<file>",
      "startLine": "<startLine>",
      "startOffset": "<startOffset>",
      "endLine": "<endLine>",
      "endOffset": "<endOffset>",
      "errorCodes": "<errorCodes>"
    },
    "name": "getCodeFixes"
  }
}

Input Schema

Name	Required	Description
`file`	Yes	File path (absolute or relative to cwd)
`endLine`	Yes	1-based end line
`endOffset`	Yes	1-based end character offset
`startLine`	Yes	1-based start line
`errorCodes`	Yes	Diagnostic error codes to get fixes for
`startOffset`	Yes	1-based start character offset

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.1Jul 12, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Adds context beyond readOnlyHint annotation by specifying it returns 'raw list of code actions' from tsserver and is for TypeScript/JavaScript. No contradictions.

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?

Two sentences with no wasted words. Front-loaded with the core action and immediately follows with usage guidance.

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?

Given no output schema, it adequately describes the return as a 'raw list of code actions'. Could mention structure or format, but sufficient for selection and invocation. Sibling differentiation is clear.

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 detailed descriptions for all 6 parameters. The description does not add new semantic information beyond the schema, but it reinforces the context of error codes and ranges.

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?

Clearly states the verb 'Get' and resource 'code fixes' for specific error codes at a range in TypeScript/JavaScript files. Distinguishes from sibling tools like getDiagnostics and getCombinedCodeFix by emphasizing it returns raw code actions.

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

Usage Guidelines5/5

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

Explicitly instructs to 'Use getDiagnostics first to discover error codes and ranges, then pass them here.', providing a clear prerequisite and usage context.

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