Skip to main content
Glama

Priority — TypeScript Compiler Intelligence

by dev.semanticreader
OverviewDiscussionsAdmin

Analyze Impact

analyze_impact
Read-onlyIdempotent

Return bounded reverse-caller impact for one exact compiler symbol.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filesNo
limitNo
offsetNo
symbolYes
compactNo
snapshotNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes
queryYes
totalYes
limitsYes
schemaYes
symbolNo
analyzerYes
coverageYes
returnedYes
snapshotYes
truncatedYes
next_offsetYes
total_foundYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed23 schema fields changed
    • addedInput schema / oneOf
      Added value: +[
+  {
+    "required": [
+      "files"
+    ]
+  },
+  {
+    "required": [
+      "snapshot"
+    ]
+  }
+]
    • removedInput schema / properties / compact / description
      Removed value: -"Prefer a token-efficient packet when this tool has a proven compact representation. Defaults to true for specialized agent tools; set false only when full verbose evidence fields are required."
    • removedInput schema / properties / files / description
      Removed value: -"Authorized JavaScript/TypeScript source files for this single request. Required every call — there is no server-side index."
    • removedInput schema / properties / files / items / properties / content / description
      Removed value: -"Full source text for that path. Only files included here are analyzed; the server does not read a repository from disk."
    • removedInput schema / properties / files / items / properties / path / description
      Removed value: -"Workspace-relative JS/TS path for this request (e.g. \"src/app.ts\"). No absolute paths, no \"..\" segments, no backslashes."
    • removedInput schema / properties / limit / description
      Removed value: -"Maximum number of items to return in this page (1–100). Prefer smaller pages when scanning large result sets."
    • removedInput schema / properties / offset / description
      Removed value: -"0-based pagination offset into the result items array. Use with limit and next_offset from the previous response."
    • addedInput schema / properties / snapshot
      Added value: +{
+  "maxLength": 100,
+  "minLength": 20,
+  "type": "string"
+}
    • removedInput schema / properties / symbol / description
      Removed value: -"Exact symbol name (e.g. \"addItem\") or a prior exact compiler symbol id from a symbols listing. Use the id when names collide across files."
    • changedInput schema / required
      Previous value: -[
-  "files",
-  "symbol"
-]New value: +[
+  "symbol"
+]
    • removedOutput schema / properties / analyzer / description
      Removed value: -"Analyzer identity including TypeScript version"
    • removedOutput schema / properties / coverage / description
      Removed value: -"Coverage and completeness markers for this analysis"
    • removedOutput schema / properties / items / description
      Removed value: -"Paged compiler facts for this query"
    • removedOutput schema / properties / limits / description
      Removed value: -"Human-readable analysis boundary statements"
    • removedOutput schema / properties / next_offset / description
      Removed value: -"Offset for the next page, or null when complete"
    • removedOutput schema / properties / query / description
      Removed value: -"Query mode that produced this packet"
    • removedOutput schema / properties / returned / description
      Removed value: -"Number of items in this page"
    • removedOutput schema / properties / schema / description
      Removed value: -"Packet schema id, e.g. semantic-reader/0.1"
    • removedOutput schema / properties / snapshot / description
      Removed value: -"Hash of the supplied file set for this request"
    • removedOutput schema / properties / symbol / description
      Removed value: -"Resolved target symbol summary when applicable"
    • removedOutput schema / properties / total / description
      Removed value: -"Total matching items before pagination caps in this response path"
    • removedOutput schema / properties / total_found / description
      Removed value: -"Total found before page slice"
    • removedOutput schema / properties / truncated / description
      Removed value: -"True when result caps truncated the set (fail-closed incomplete, not absence proof)"
  2. Changed1 schema field changed
    • addedInput schema / properties / compact
      Added value: +{
+  "default": true,
+  "description": "Prefer a token-efficient packet when this tool has a proven compact representation. Defaults to true for specialized agent tools; set false only when full verbose evidence fields are required.",
+  "type": "boolean"
+}
  3. Changed8 schema fields changed
    • addedInput schema / properties / files / description
      Added value: +"Authorized JavaScript/TypeScript source files for this single request. Required every call — there is no server-side index."
    • addedInput schema / properties / files / items / properties / content / description
      Added value: +"Full source text for that path. Only files included here are analyzed; the server does not read a repository from disk."
    • addedInput schema / properties / files / items / properties / path / description
      Added value: +"Workspace-relative JS/TS path for this request (e.g. \"src/app.ts\"). No absolute paths, no \"..\" segments, no backslashes."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of items to return in this page (1–100). Prefer smaller pages when scanning large result sets."
    • addedInput schema / properties / offset / description
      Added value: +"0-based pagination offset into the result items array. Use with limit and next_offset from the previous response."
    • addedInput schema / properties / symbol / description
      Added value: +"Exact symbol name (e.g. \"addItem\") or a prior exact compiler symbol id from a symbols listing. Use the id when names collide across files."
    • changedInput schema / required
      Previous value: -[
-  "files"
-]New value: +[
+  "files",
+  "symbol"
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "analyzer": {
+      "description": "Analyzer identity including TypeScript version",
+      "type": "string"
+    },
+    "coverage": {
+      "additionalProperties": {},
+      "description": "Coverage and completeness markers for this analysis",
+      "type": "object"
+    },
+    "items": {
+      "description": "Paged compiler facts for this query",
+      "items": {
+        "additionalProperties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "limits": {
+      "description": "Human-readable analysis boundary statements",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "next_offset": {
+      "description": "Offset for the next page, or null when complete",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "query": {
+      "description": "Query mode that produced this packet",
+      "type": "string"
+    },
+    "returned": {
+      "description": "Number of items in this page",
+      "type": "number"
+    },
+    "schema": {
+      "description": "Packet schema id, e.g. semantic-reader/0.1",
+      "type": "string"
+    },
+    "snapshot": {
+      "description": "Hash of the supplied file set for this request",
+      "type": "string"
+    },
+    "symbol": {
+      "description": "Resolved target symbol summary when applicable"
+    },
+    "total": {
+      "description": "Total matching items before pagination caps in this response path",
+      "type": "number"
+    },
+    "total_found": {
+      "description": "Total found before page slice",
+      "type": "number"
+    },
+    "truncated": {
+      "description": "True when result caps truncated the set (fail-closed incomplete, not absence proof)",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "schema",
+    "analyzer",
+    "snapshot",
+    "query",
+    "items",
+    "total",
+    "total_found",
+    "returned",
+    "truncated",
+    "next_offset",
+    "coverage",
+    "limits"
+  ],
+  "type": "object"
+}
  4. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description only needs to add context beyond that. It usefully adds 'bounded' and 'exact compiler symbol' semantics, clarifying pagination and match behavior, but it does not contradict the annotations.

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 a single sentence with no filler. The core verb, resource, and key qualifiers are front-loaded, and every word contributes to the meaning.

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?

Even with a valid output schema and safety annotations, the description is too thin for a tool with a oneOf input mode and six parameters. An agent cannot infer when to supply files versus snapshot or what compact does. More operational context is needed for reliable invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, but it only hints at the symbol and boundedness. It does not explain the semantic difference between files and snapshot, the meaning of compact, or how offset beyond a numeric boundary works. This is insufficient for six parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses the specific verb 'Return' and identifies a precise resource: bounded reverse-caller impact for one exact compiler symbol. This scope distinguishes it from sibling tools like find_references or get_importers, though it does not explicitly name them.

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 for exact-symbol reverse-caller impact queries but provides no explicit when-to-use guidance or alternatives. It leaves the agent to infer that this is the appropriate tool for bounded caller analysis rather than stating when not to use it.

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

All Priority — TypeScript Compiler Intelligence toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources