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

ts-diagnostics-mcp

by GNARC0TICS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_package_diagnostics

Retrieve TypeScript diagnostics for a specific package in a monorepo to filter errors by workspace, eliminating the need to run tsc repeatedly.

Instructions

Get TypeScript diagnostics for a specific package in a monorepo. Useful for filtering diagnostics by workspace.

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": {
      "packageName": "<packageName>"
    },
    "name": "get_package_diagnostics"
  }
}

Input Schema

NameRequiredDescriptionDefault
packageNameYesName of the package (e.g., "@degentalk/server")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries full behavioral burden. It only states the basic function without disclosing side effects, prerequisites, error behavior, or response format.

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 with no wasted words, front-loaded with the tool's purpose.

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?

Given the lack of output schema and annotations, the description fails to explain what the diagnostics output looks like, error cases, or how it relates to other diagnostic tools. The provided context is insufficient for correct invocation.

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 description coverage is 100%, with the parameter clearly documented. The tool description does not add additional meaning beyond the schema, so 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 explicitly states the verb 'Get' and the resource 'TypeScript diagnostics for a specific package', and distinguishes from siblings like get_all_diagnostics by focusing on a single package.

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?

The description indicates it is 'useful for filtering diagnostics by workspace', providing clear context for when to use. It does not explicitly state when not to use, but the sibling tools imply 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