The Cure Protocol

get_mind_signal

Read-only

USE WHEN the question is about the SI (super intelligence) economy: where its four capitals, Material, Intelligence, Network, Diversity, are moving, and how concentrated that movement is. Returns counts, directional pulse, a sparkline, a diversity/conscience index and top signals for each of the four capitals (M=Material, I=Intelligence, N=Network, D=Diversity) over a trailing window. NEXT: call get_trends_signal for feed shape and the crypto-distribution lens, or get_batch_signals to pull all three signals in one round-trip. This measures published attention and announced capital, not settled transactions.

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

Input Schema

Name	Required	Description	Default
`days`	No	Trailing window length in days (1–120). Default 30.
`disease`	No	Narrow the capital breakdown to signals matching this keyword.

Output Schema

Name	Required	Description	Default
`data`	No	The answer. Shape depends on the tool; describe_tool documents it.
`_meta`	No	source, generatedAt, sources (per-source lastSyncedAt and ageHours), rateLimit, disclaimer.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "_meta": {
+      "additionalProperties": {},
+      "description": "source, generatedAt, sources (per-source lastSyncedAt and ageHours), rateLimit, disclaimer.",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "data": {
+      "description": "The answer. Shape depends on the tool; describe_tool documents it."
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedOct 24, 2026
- addedInput schema / properties / disease / maxLength
```
Added value: +20000
```
First observedOct 18, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds genuinely non-obvious behavioral context about what the data represents and does not represent ('not settled transactions'). It stops short of describing freshness/recency guarantees or rate limits, so it is strong but not exhaustive.

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 trigger condition is front-loaded, the return inventory follows, then routing alternatives, then the interpretive caveat. Three dense sentences with no filler; the parenthetical capital abbreviations are the only mild redundancy.

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?

With an output schema present and annotations covering safety, the description only needs to cover intent and routing, both of which it does. Scope caveat, return shape and sibling alternatives are all present, so an agent can call this correctly on the first attempt.

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%, so both parameters are documented in the schema and the baseline applies. The description only echoes the trailing-window concept ('over a trailing window') and never mentions the 'disease' keyword filter at all, so it adds little meaning beyond the structured fields.

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?

Names a specific resource (the SI economy's four capitals: Material, Intelligence, Network, Diversity) and enumerates exactly what is returned (counts, directional pulse, sparkline, diversity/conscience index, top signals). It also names the sibling tools that cover adjacent ground, so an agent can separate it from get_trends_signal and get_batch_signals without opening a schema.

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?

Opens with an explicit 'USE WHEN the question is about the SI economy' trigger and follows with concrete routing ('NEXT: call get_trends_signal ... or get_batch_signals'). It even states a scope boundary — published attention and announced capital, not settled transactions — which functions as a when-not signal.

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

All The Cure Protocol tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?