SigRank MCP server

simulate_change

Read-onlyIdempotent

Simulate proposed token-mix changes to compute exact Yield delta, class change, and per-metric diffs. See the payoff before changing your workflow.

Instructions

The first PRESCRIPTIVE SigRank tool — 'what if I changed my token mix?' Takes your current 4 pillars (input/output/cacheCreate/cacheRead) and one or more proposed changes, runs the canonical cascade on BOTH the current and simulated values, and returns the exact Υ Yield delta, class change, and per-metric diffs. This is the 'show me the payoff before I do the work' primitive: no network, no submission, pure local math. Use it to answer 'would increasing my cache-read by 50k tokens actually move my class?' before you change your workflow. Accepts the current pillars as JSON or 4 numbers (same as rank_paste) plus a changes object with any of the 4 pillar names mapped to new absolute values OR relative deltas (e.g. {cacheRead: '+50000'} or {input: 800000}).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`text`	Yes	Current token pillars — ccusage JSON or "input output cacheCreate cacheRead" (same format as rank_paste).
`changes`	Yes	Proposed changes to apply. Keys: input, output, cacheCreate, cacheRead. Values are either absolute numbers (replace) or strings starting with +/- for relative deltas (add/subtract). Omitted pillars are unchanged.

Output Schema

TableJSON Schema

Name	Required	Description
`current`	No
`simulated`	No
`yield_delta`	No	Υ Yield change (simulated - current)
`class_change`	No	Class tier change description
`metric_diffs`	No	Per-metric before/after diffs

Schema Changelog

Changes observed during successful MCP inspections.

Changed18 schema fields changedv0.19.6Aug 11, 2026

changedOutput schema / properties / current / properties / class / description

Previous value: -"Operator class tier"New value: +"Operator class tier (dev10x taxonomy)"

changedOutput schema / properties / current / properties / class / enum

Previous value: -[
-  "Burner",
-  "Builder",
-  "10xer"
-]New value: +[
+  "ARCH+ I",
+  "ARCH+ II",
+  "ARCH+ III",
+  "ARCH I",
+  "ARCH II",
+  "ARCH III",
+  "POWER I",
+  "POWER II",
+  "POWER III",
+  "BASE I",
+  "BASE II",
+  "BASE III",
+  "SEEKER I",
+  "SEEKER II",
+  "SEEKER III",
+  "REFINER I",
+  "REFINER II",
+  "REFINER III",
+  "BEARER I",
+  "BEARER II",
+  "BEARER III",
+  "IGNITER I",
+  "IGNITER II",
+  "IGNITER III",
+  "UNCLASSED"
+]

addedOutput schema / properties / current / properties / dev10x

Added value: +{
+  "description": "10xDEV score (log10 of the cascade product)",
+  "type": "number"
+}

addedOutput schema / properties / current / properties / mode

Added value: +{
+  "description": "Detected working mode (BUILD/EDIT/DEBUG/MAINTAIN/IDLE) + confidence",
+  "type": "object"
+}

addedOutput schema / properties / current / properties / pillars

Added value: +{
+  "description": "The four raw token pillars the cascade was computed from",
+  "type": "object"
+}

removedOutput schema / properties / current / properties / tenx_dev

Removed value: -{
-  "description": "10xDEV score",
-  "type": "number"
-}

addedOutput schema / properties / current / properties / yield

Added value: +{
+  "description": "Υ Yield — the headline efficiency metric (Cache Reads × Output / Input²)",
+  "type": "number"
+}

removedOutput schema / properties / current / properties / yield_

Removed value: -{
-  "description": "Υ Yield — the headline efficiency metric (Cache Reads × Output / Input²)",
-  "type": "number"
-}

changedOutput schema / properties / current / required

Previous value: -[
-  "yield_",
-  "class"
-]New value: +[
+  "yield",
+  "class"
+]

changedOutput schema / properties / simulated / properties / class / description

Previous value: -"Operator class tier"New value: +"Operator class tier (dev10x taxonomy)"

changedOutput schema / properties / simulated / properties / class / enum

Previous value: -[
-  "Burner",
-  "Builder",
-  "10xer"
-]New value: +[
+  "ARCH+ I",
+  "ARCH+ II",
+  "ARCH+ III",
+  "ARCH I",
+  "ARCH II",
+  "ARCH III",
+  "POWER I",
+  "POWER II",
+  "POWER III",
+  "BASE I",
+  "BASE II",
+  "BASE III",
+  "SEEKER I",
+  "SEEKER II",
+  "SEEKER III",
+  "REFINER I",
+  "REFINER II",
+  "REFINER III",
+  "BEARER I",
+  "BEARER II",
+  "BEARER III",
+  "IGNITER I",
+  "IGNITER II",
+  "IGNITER III",
+  "UNCLASSED"
+]

addedOutput schema / properties / simulated / properties / dev10x

Added value: +{
+  "description": "10xDEV score (log10 of the cascade product)",
+  "type": "number"
+}

addedOutput schema / properties / simulated / properties / mode

Added value: +{
+  "description": "Detected working mode (BUILD/EDIT/DEBUG/MAINTAIN/IDLE) + confidence",
+  "type": "object"
+}

addedOutput schema / properties / simulated / properties / pillars

Added value: +{
+  "description": "The four raw token pillars the cascade was computed from",
+  "type": "object"
+}

removedOutput schema / properties / simulated / properties / tenx_dev

Removed value: -{
-  "description": "10xDEV score",
-  "type": "number"
-}

addedOutput schema / properties / simulated / properties / yield

Added value: +{
+  "description": "Υ Yield — the headline efficiency metric (Cache Reads × Output / Input²)",
+  "type": "number"
+}

removedOutput schema / properties / simulated / properties / yield_

Removed value: -{
-  "description": "Υ Yield — the headline efficiency metric (Cache Reads × Output / Input²)",
-  "type": "number"
-}

changedOutput schema / properties / simulated / required

Previous value: -[
-  "yield_",
-  "class"
-]New value: +[
+  "yield",
+  "class"
+]

Changed1 schema field changedv0.16.0Jul 7, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "class_change": {
+      "description": "Class tier change description",
+      "type": "string"
+    },
+    "current": {
+      "properties": {
+        "card": {
+          "description": "Deterministic prose summary of the cascade result",
+          "type": "string"
+        },
+        "class": {
+          "description": "Operator class tier",
+          "enum": [
+            "Burner",
+            "Builder",
+            "10xer"
+          ],
+          "type": "string"
+        },
+        "leverage": {
+          "description": "Cr/I — cache reads divided by input",
+          "type": "number"
+        },
+        "snr": {
+          "description": "Signal-to-noise ratio",
+          "type": "number"
+        },
+        "tenx_dev": {
+          "description": "10xDEV score",
+          "type": "number"
+        },
+        "velocity": {
+          "description": "O/I — output divided by input",
+          "type": "number"
+        },
+        "warnings": {
+          "description": "Parse or data warnings if any",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "yield_": {
+          "description": "Υ Yield — the headline efficiency metric (Cache Reads × Output / Input²)",
+          "type": "number"
+        }
+      },
+      "required": [
+        "yield_",
+        "class"
+      ],
+      "type": "object"
+    },
+    "metric_diffs": {
+      "description": "Per-metric before/after diffs",
+      "type": "object"
+    },
+    "simulated": {
+      "properties": {
+        "card": {
+          "description": "Deterministic prose summary of the cascade result",
+          "type": "string"
+        },
+        "class": {
+          "description": "Operator class tier",
+          "enum": [
+            "Burner",
+            "Builder",
+            "10xer"
+          ],
+          "type": "string"
+        },
+        "leverage": {
+          "description": "Cr/I — cache reads divided by input",
+          "type": "number"
+        },
+        "snr": {
+          "description": "Signal-to-noise ratio",
+          "type": "number"
+        },
+        "tenx_dev": {
+          "description": "10xDEV score",
+          "type": "number"
+        },
+        "velocity": {
+          "description": "O/I — output divided by input",
+          "type": "number"
+        },
+        "warnings": {
+          "description": "Parse or data warnings if any",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "yield_": {
+          "description": "Υ Yield — the headline efficiency metric (Cache Reads × Output / Input²)",
+          "type": "number"
+        }
+      },
+      "required": [
+        "yield_",
+        "class"
+      ],
+      "type": "object"
+    },
+    "yield_delta": {
+      "description": "Υ Yield change (simulated - current)",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

Addedv0.6.10Jul 4, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=true, idempotentHint=true), the description discloses key behavioral traits: it runs the canonical cascade on BOTH current and simulated values, returns an exact yield delta (implying deterministic math), and specifically notes 'no network, no submission, pure local math.' This adds meaningful context about what the tool does and does not do.

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 front-loaded with the core purpose, then explains the use case, and finally details the input format. Every sentence earns its place: it explains what the tool does, why to use it, and how to use it. The length is justified given the tool's complexity, and there is no filler.

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?

The description covers the tool's purpose, inputs, outputs (yield delta, class change, per-metric diffs), and constraints (local, read-only, no submission). It also includes a practical example use case. Given the presence of an output schema and a clear input schema, the description is complete enough for an agent to decide when and how to invoke the 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?

The schema already provides full descriptions for both parameters (100% coverage). The description adds value by clarifying that the input format is 'same as rank_paste', giving explicit examples for relative deltas ('{cacheRead: '+50000'}') and absolute values ('{input: 800000}'), and restating the semantics of omitted pillars. This reinforces the schema without being redundant.

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 identifies the tool as a 'what if I changed my token mix?' simulation that computes yield deltas, class changes, and per-metric diffs. It uses a specific verb ('simulate') and resource ('token mix'), and explicitly distinguishes itself from siblings as 'the first PRESCRIPTIVE SigRank tool' and a 'show me the payoff before I do the work' primitive.

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 states when to use it ('before you change your workflow') and provides a concrete example question ('would increasing my cache-read by 50k tokens actually move my class?'). It also signals when not to use it: 'no network, no submission' and 'pure local math', implying it is for analysis only. However, it does not explicitly name alternative sibling tools, so it falls short of a full 5.

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