The Cure Protocol

get_trends_signal

Read-only

USE WHEN you need attention dynamics rather than levels: what is accelerating or decelerating in coverage, and where attention concentrates across categories and research domains (7-day momentum, 30-day daily series). Also returns the curated 2026 crypto token-generation-event list scored by how much capital widens access versus concentrates in insiders, contrasted with live cure-research capital. NEXT: get_mind_signal for the capital levels behind the momentum. Set series=false to slim the payload.

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_trends_signal"
  }
}

Input Schema

Name	Required	Description	Default
`series`	No	Include the 30-day daily series. false slims the payload.
`disease`	No	Narrow the signal section to matching stories.
`include`	No	Comma-separated sections: signal, crypto.	signal,crypto

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"
+}

Changed3 schema fields changedOct 24, 2026

addedInput schema / properties / disease / maxLength
```
Added value: +20000
```

addedInput schema / properties / include / anyOf

Added value: +[
+  {
+    "maxLength": 2000,
+    "type": "string"
+  },
+  {
+    "items": {
+      "maxLength": 200,
+      "type": "string"
+    },
+    "maxItems": 100,
+    "minItems": 1,
+    "type": "array"
+  }
+]

removedInput schema / properties / include / type
```
Removed value: -"string"
```

First observedOct 18, 2026

TDQS

A4.1/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 meaningful context about contents (7-day momentum, 30-day daily series, curated crypto TGE list contrasted with live cure-research capital) and a payload trade-off. It does not discuss freshness or computation cost, but adds solid behavioral value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The critical 'USE WHEN' clause is front-loaded and the description is short overall. The middle sentence is a run-on that stitches crypto TGE scoring and cure-research capital into one breath, slightly hurting scannability.

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?

With an output schema and read-only annotations already present, the description needs only to explain what the signal covers and how to route between it and get_mind_signal, which it does. It omits mention of the include/disease narrowing behavior, but the schema carries that.

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 coverage is 100%, so all three parameters are already documented. The description only reinforces the series=false slimming behavior and says nothing about the disease filter or the include section list beyond what the schema provides. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource (attention dynamics: momentum and 30-day series across categories and research domains) and distinguishes it from the level-oriented sibling get_mind_signal. The purpose is clear, though the crypto-token-generation-event clause is dense and slightly obscures the core 'trends' framing.

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 opens with an explicit 'USE WHEN you need attention dynamics rather than levels,' names the alternative ('NEXT: get_mind_signal for the capital levels'), and gives a payload-slimming instruction (series=false). The selection condition and follow-up path are both stated.

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?