Skip to main content
Glama
Sign In
ts-diagnostics-mcp

ts-diagnostics-mcp

by GNARC0TICS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_file_diagnostics

Get TypeScript diagnostics for a specific file quickly, without needing to run tsc on the whole project.

Instructions

Get TypeScript diagnostics for a specific file. Much faster than running tsc on the whole project.

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": {
      "filePath": "<filePath>"
    },
    "name": "get_file_diagnostics"
  }
}

Input Schema

NameRequiredDescriptionDefault
filePathYesPath to the TypeScript file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. States it gets diagnostics but does not disclose what diagnostics include (e.g., errors, warnings) or any side effects. Adds speed disclaimer but lacks depth.

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 concise sentences, no unnecessary words, front-loaded with the core purpose.

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?

Adequate for a simple one-parameter tool without output schema. Explains purpose and speed advantage but lacks details on return format or potential errors.

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 provides complete description of the single parameter 'filePath' (100% coverage). Description does not add extra 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?

Description clearly states it gets TypeScript diagnostics for a specific file and highlights its speed advantage over running tsc on the whole project, distinguishing it from sibling tools like get_all_diagnostics.

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?

Implicitly suggests use when needing diagnostics for a single file quickly, but lacks explicit when-not or alternative guidance. The sibling list provides context but the description itself doesn't direct to alternatives.

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

Deploy Server

Other Tools