The Cure Protocol

list_cure_hypotheses

Read-only

LIST T1D CURE HYPOTHESES with their falsifiable predictions, lifecycle state (and whether the Agent Council set it) and evidence counts for and against. NEXT: submit_evidence with hypothesisId, or propose_cure_hypothesis.

Input Schema

Name	Required	Description
`limit`	No	How many.
`track`	No	A, B, C, D, E or unassigned.
`cursor`	No	Opaque cursor. Pass _meta.pagination.nextCursor from the previous call unchanged to get the next page; omit it to start at the beginning.
`offset`	No	Pagination offset.

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

addedInput schema / properties / cursor

Added value: +{
+  "description": "Opaque cursor. Pass _meta.pagination.nextCursor from the previous call unchanged to get the next page; omit it to start at the beginning.",
+  "maxLength": 200,
+  "type": "string"
+}

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

Changed2 schema fields changedOct 24, 2026
- changedInput schema / properties / offset / maximum
```
Previous value: -9007199254740991New value: +100000
```
- addedInput schema / properties / track / maxLength
```
Added value: +20000
```
AddedOct 19, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, so safety is already covered. The description adds genuine value on top: what the records contain (predictions, lifecycle state, council-set flag, for/against evidence counts), which tells the agent what it can decide after calling. It does not mention ordering, pagination behavior, or result size, so it is not fully transparent.

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?

One front-loaded sentence covering purpose and payload, one compact routing sentence. Zero filler. The 'NEXT:' shorthand is terse to the point of being slightly telegraphic, but every clause earns its place.

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?

Output schema exists, so return shape need not be explained; annotations cover the safety profile; all parameters are documented in schema. The description covers purpose and next step, leaving only minor gaps around filtering and pagination that the schema already partially handles.

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% with all four parameters documented, so the schema carries parameter meaning and the baseline applies. The description adds nothing about limit, track, cursor, or offset — notably the track filter and paging, which materially change the call, go unmentioned.

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?

States a specific verb+resource (LIST T1D CURE HYPOTHESES) and enumerates what the listing contains: falsifiable predictions, lifecycle state and whether the Agent Council set it, and evidence counts for and against. That is well beyond a restatement of the name. It stops short of naming the sibling it is not (read_cure_hypothesis for a single item, search_cure_evidence for evidence lookup), so an agent must infer the split from the verb alone.

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 'NEXT: submit_evidence with hypothesisId, or propose_cure_hypothesis' clause gives concrete downstream routing and even the key field to carry forward, which is real usage guidance. There are no when-not conditions or explicit alternatives for retrieval paths (single read vs broad listing), so it is clear context without exclusions.

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?