SigRank MCP server

tokenpull_compare

Read-only

Pull token usage from four local sources in parallel, compare side-by-side with delta percentages, and compute cascade scores to validate numbers or expose discrepancies.

Instructions

Pull token usage from ALL four local sources in parallel — tokenpull (JSONL canon), ccusage CLI, token-dashboard SQLite, and tokscale report — and return them side-by-side with delta % vs tokenpull as the baseline. Also computes the cascade (Υ, SNR, Leverage, class) for each source so you can see how each verifier scores. Useful for validating your numbers before submitting, or understanding discrepancies between tools. Claude only for token-dash; codex and others use tokenpull + ccusage + tokscale. Token-only, on-device.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`platform`	No	platform to compare (default: claude). token-dash and App only available for claude.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`sources`	No	Side-by-side comparison of each token source
`platform`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.19.7Aug 19, 2026

changedInput schema / properties / platform / enum

Previous value: -[
-  "amp",
-  "kimi",
-  "qwen",
-  "pi",
-  "openclaw",
-  "droid",
-  "codebuff",
-  "gemini",
-  "copilot",
-  "opencode",
-  "goose",
-  "kilo",
-  "hermes",
-  "devin",
-  "other",
-  "omp",
-  "proxy",
-  "claude",
-  "codex"
-]New value: +[
+  "amp",
+  "kimi",
+  "qwen",
+  "pi",
+  "openclaw",
+  "droid",
+  "codebuff",
+  "gemini",
+  "copilot",
+  "opencode",
+  "goose",
+  "kilo",
+  "hermes",
+  "devin",
+  "other",
+  "omp",
+  "proxy",
+  "claude",
+  "codex",
+  "grok"
+]

Changed10 schema fields changedv0.19.6Aug 11, 2026

changedInput schema / properties / platform / enum

Previous value: -[
-  "amp",
-  "kimi",
-  "qwen",
-  "pi",
-  "openclaw",
-  "droid",
-  "codebuff",
-  "gemini",
-  "copilot",
-  "opencode",
-  "goose",
-  "kilo",
-  "hermes",
-  "devin",
-  "other",
-  "claude",
-  "codex"
-]New value: +[
+  "amp",
+  "kimi",
+  "qwen",
+  "pi",
+  "openclaw",
+  "droid",
+  "codebuff",
+  "gemini",
+  "copilot",
+  "opencode",
+  "goose",
+  "kilo",
+  "hermes",
+  "devin",
+  "other",
+  "omp",
+  "proxy",
+  "claude",
+  "codex"
+]

changedOutput schema / properties / sources / items / properties / cascade / properties / class / description
```
Previous value: -"Operator class tier"New value: +"Operator class tier (dev10x taxonomy)"
```

changedOutput schema / properties / sources / items / properties / cascade / 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 / sources / items / properties / cascade / properties / dev10x

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

addedOutput schema / properties / sources / items / properties / cascade / properties / mode

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

addedOutput schema / properties / sources / items / properties / cascade / properties / pillars

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

removedOutput schema / properties / sources / items / properties / cascade / properties / tenx_dev
```
Removed value: -{
-  "description": "10xDEV score",
-  "type": "number"
-}
```

addedOutput schema / properties / sources / items / properties / cascade / properties / yield

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

removedOutput schema / properties / sources / items / properties / cascade / properties / yield_

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

changedOutput schema / properties / sources / items / properties / cascade / required

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

Changed1 schema field changedv0.18.1Jul 14, 2026

changedInput schema / properties / platform / enum

Previous value: -[
-  "amp",
-  "kimi",
-  "qwen",
-  "pi",
-  "openclaw",
-  "droid",
-  "codebuff",
-  "gemini",
-  "copilot",
-  "opencode",
-  "goose",
-  "kilo",
-  "hermes",
-  "claude",
-  "codex"
-]New value: +[
+  "amp",
+  "kimi",
+  "qwen",
+  "pi",
+  "openclaw",
+  "droid",
+  "codebuff",
+  "gemini",
+  "copilot",
+  "opencode",
+  "goose",
+  "kilo",
+  "hermes",
+  "devin",
+  "other",
+  "claude",
+  "codex"
+]

Changed1 schema field changedv0.16.0Jul 7, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "platform": {
+      "type": "string"
+    },
+    "sources": {
+      "description": "Side-by-side comparison of each token source",
+      "items": {
+        "properties": {
+          "cascade": {
+            "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"
+          },
+          "delta_pct": {
+            "description": "Delta % vs tokenpull baseline",
+            "type": "object"
+          },
+          "pillars": {
+            "type": "object"
+          },
+          "source": {
+            "description": "Source name (tokenpull, ccusage, token-dash, tokscale)",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "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?

The description adds critical context beyond the readOnlyHint: it promises parallel execution, returns 'delta % vs tokenpull as the baseline', computes cascade metrics for each source, and emphasizes it is 'Token-only, on-device'. The readOnlyHint aligns with the non-destructive read nature described, and the openWorldHint aligns with the fixed set of local sources. No contradiction.

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 two sentences with high information density, front-loaded with the core function and lists key features and usage. Every sentence earns its place, and it remains concise despite covering many aspects.

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?

Given the tool's complexity (multiple sources, baseline comparison, cascade computation), the description covers the purpose, the data sources, the key output (delta % and cascade), and usage context. An output schema exists for return values, so the description doesn't need detailed output specs. The description is fully self-contained for an AI agent to select and invoke correctly.

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 schema description covers 100% of the parameter, so baseline is 3. The description adds context about platform-specific source usage, but the description does not explain the parameter format or behavior beyond what the schema already provides.

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 'Pull token usage from ALL four local sources in parallel' and specifies the exact sources and computation of delta percentages and cascade metrics. It distinguishes itself from siblings like 'tokenpull' by emphasizing the comparative and validating nature.

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?

It explicitly says 'Useful for validating your numbers before submitting, or understanding discrepancies between tools' and provides guidance on which platforms use which sources ('Claude only for token-dash; codex and others use tokenpull + ccusage + tokscale'). This is clear when-to-use context and differentiates from alternative tools.

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

tokenpull_compare

Instructions

Input Schema

Output Schema

Schema Changelog

TDQS

Other Tools