Stellaris MCP

Overview Schema Source Related Servers Discussions Admin

detect_significant_changes

Identify technically significant sessions by analyzing git diff changes (lines/files) and graph cycles to prompt memory storage.

Instructions

Heuristic detector for "was this session technically significant?" Returns significant:true + signals if git diff exceeds thresholds (default: 100 lines or 5 files) or graph has cycles. Intended for Stop/SessionEnd hooks to prompt memorization via nova-mind-cloud storeMemory. No API.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "detect_significant_changes"
  }
}

Input Schema

Name	Required	Description
`base`	No	Git base ref to diff against (default: HEAD)
`lines_threshold`	No	Min total lines changed to be significant (default: 100)
`files_threshold`	No	Min files changed to be significant (default: 5)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv4.4.0Jun 8, 2026

TDQS

A3.9/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 full burden. It discloses the heuristic nature, thresholds, and that it returns a boolean and signals. However, it omits details on error handling, side effects, and the meaning of 'No API', leaving room for ambiguity.

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 three sentences, each essential: purpose, logic, and usage context. It is front-loaded with the main verb and resource, and contains no superfluous words.

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

Completeness3/5

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

Given the lack of an output schema, the description partially explains return values but does not detail the 'signals' output or potential error conditions. More information on the output format would improve completeness.

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 each parameter having a description. The tool description repeats default values but adds no new meaning beyond what the schema already provides, so 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 defines the tool's role as a heuristic detector for session technical significance, specifying criteria (git diff thresholds, graph cycles) and output (significant:true + signals). It is distinct from sibling tools, which focus on code analysis and project health.

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 explicitly states the intended use in Stop/SessionEnd hooks and integration with storeMemory. However, it does not discuss when not to use the tool or mention alternative tools, which would strengthen guidance.

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