ts-mcp-server

Overview Schema Source Related Servers Discussions Admin

File References

fileReferences

Read-only

Retrieve all files that import or reference a specified file in a project. Generates the reverse dependency graph for targeted file analysis.

Instructions

Finds every file that imports or references a given file. The reverse dependency graph for a single file.

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>"
    },
    "name": "fileReferences"
  }
}

Input Schema

Name	Required	Description	Default
`file`	Yes	File path (absolute or relative to cwd)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.1Jul 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=true. Description adds specific behavioral context (finding importing/referencing files). 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?

Single sentence, no filler, front-loaded with purpose. Every word is informative.

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 with annotations. Does not describe output format but implies a list of files. Could be more complete but sufficient.

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%, so the schema fully documents the 'file' parameter. Description does not add further meaning beyond what is in 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?

Clearly states the verb 'finds' and resource 'every file that imports or references a given file'. Distinguishes from sibling 'references' by specifying it is the reverse dependency graph.

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?

Provides clear context ('reverse dependency graph') but does not explicitly state when to use this tool versus alternatives like 'references'. No exclusions mentioned.

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