The Cure Protocol

get_hope_signal

Read-only

USE WHEN you want the headline picture of cure progress: how much active clinical-trial activity exists overall and per disease, plus the latest curated cure-research index. This is a SUMMARY signal. NEXT: for actual trial records, worldwide and deduplicated, call search_world_trials; for the structure of a field call get_trial_landscape. IMPORTANT: the trial counts here come from a US ClinicalTrials.gov census that is deliberately kept separate from the multi-registry world index — never add the two together.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Research articles per page (1–50).
`cursor`	No	Opaque pagination cursor from a previous _meta. Mutually exclusive with offset.
`offset`	No	Zero-based offset. Ignored if cursor is given.
`disease`	No	Filter research articles by disease keyword.
`include`	No	Comma-separated sections: trials, research, stats.	trials,research,stats

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

Changed5 schema fields changedOct 24, 2026

addedInput schema / properties / cursor / maxLength
```
Added value: +20000
```
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"
```

changedInput schema / properties / offset / maximum

Previous value: -9007199254740991New value: +100000

First observedOct 18, 2026

TDQS

A4.4/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 the safety profile is covered. The description adds real behavioral context beyond that: the trial counts come from a US ClinicalTrials.gov census deliberately kept separate from the multi-registry world index, with an explicit 'never add the two together' warning. This provenance/aggregation caveat is a meaningful disclosure, though the description stops short of describing pagination or result-shape behavior.

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?

Front-loaded with 'USE WHEN,' then 'NEXT,' then 'IMPORTANT,' giving a clear scannable structure. Every sentence carries routing or caveat value; the only mild cost is density, but nothing is redundant or padding.

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, the description needn't explain return values, and annotations cover the safety profile. It supplies the remaining pieces an agent needs: what the signal summarizes, which siblings to use for detail, and the critical warning not to combine the two trial-count sources. Complete for correct invocation.

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 the schema already documents limit, cursor, offset, disease, and include. The description adds no parameter-level meaning — notably it does not clarify that limit/disease/offset appear to be scoped to the research-article section rather than the trial counts, which is the one place a sentence would have added value. Baseline 3 applies.

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?

States a specific resource and scope: headline picture of cure progress with active clinical-trial activity (overall and per disease) plus the curated cure-research index. It explicitly frames itself as a SUMMARY signal and names siblings it is not, so an agent can distinguish it from search_world_trials or get_trial_landscape without opening any 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' condition and then routes the agent: 'NEXT: for actual trial records ... call search_world_trials; for the structure of a field call get_trial_landscape.' The alternative and the condition that selects it are both stated, leaving nothing to inference.

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?