Stellaris MCP

Overview Schema Source Related Servers Discussions Admin

get_symbol

Fetch a symbol's full source code and file context, including imports and related symbols, for detailed inspection.

Instructions

STEP 4 of token-efficient exploration — the only step that returns full source. Fetches ONE symbol (function/class/type) with file context (imports, siblings, warnings). Use ONLY after search_code/get_file_outline/get_file_folded identified the symbol. No API.

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

Input Schema

Name	Required	Description
`file`	Yes	Relative file path from project root (e.g., "src/tools/searchCode.ts")
`name`	Yes	Symbol name to retrieve (e.g., "handleSearchCode", "SearchResult")
`context`	No	Include file context: imports, exports, sibling symbols, warnings (default: true). Set to false for raw source only.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv4.4.0Jun 8, 2026

TDQS

A4.4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that it returns 'full source' with context (imports, siblings, warnings) and explains the context parameter. However, it omits details like error handling, idempotency, or what happens if the symbol is not found.

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 sentences: the first defines purpose and output, the second gives usage guidance. Front-loaded with the step number. No fluff.

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?

Given no output schema, the description adequately describes the return (full source with context). It covers the main parameters and usage constraints. However, missing details like error responses or performance implications, but acceptable for a simple retrieval tool.

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

Parameters4/5

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

Schema coverage is 100%, baseline 3. The description adds value by explaining the context parameter's default (true) and what it includes ('imports, exports, sibling symbols, warnings'), going beyond the schema's brief description.

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 verb 'fetches' and the resource 'ONE symbol (function/class/type)' with file context. It positions itself as 'STEP 4 of token-efficient exploration' and notes it's 'the only step that returns full source,' distinguishing it from sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use: 'Use ONLY after `search_code`/`get_file_outline`/`get_file_folded` identified the symbol.' It also says 'No API,' implying it's for in-context code base retrieval, not external APIs.

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