Stellaris MCP

Overview Schema Source Related Servers Discussions Admin

get_dependents

Find all files that import a specified file, revealing its dependents and reverse dependencies. Plan refactoring or assess change impact.

Instructions

Get the files that import a given file (its dependents / reverse dependencies). Shows what other code relies on this file. Requires a prior reindex to build the dependency graph. No API call needed.

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": "get_dependents"
  }
}

Input Schema

Name	Required	Description	Default
`file`	Yes	Relative file path from project root (e.g., "src/tools/searchCode.ts")

Schema Changelog

Changes observed during successful MCP inspections.

First observedv4.4.0Jun 8, 2026

TDQS

A4.3/5.0

Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses that no API call is needed and requires a prior reindex, which are important behavioral traits. No destructive or side effects are mentioned, but the tool is read-only by nature.

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 concise, with three sentences that front-load the purpose and add essential context (prerequisite, no API call). Every sentence contributes meaningfully.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one parameter and no output schema, the description is complete: it explains the purpose, the input, the prerequisite, and a behavioral note. No gaps are apparent.

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?

The single parameter 'file' is fully described in the schema (100% coverage). The description adds no additional semantic information beyond what the schema provides, so a baseline score of 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 clearly states the tool returns files that import a given file (dependents/reverse dependencies), distinguishing it from sibling tools like get_dependencies which likely return forward dependencies. It also specifies the prerequisite of prior reindex.

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 mentions a key prerequisite (prior reindex), which guides proper usage. It does not explicitly state when to use this tool over alternatives, but the purpose is clear enough for context.

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