The Cure Protocol

register_dead_end

WRITES: RECORD A DEAD END the moment an approach stops: what you tried, how far it got, exactly where and why it stopped, and what would change it. It never blocks anyone, and it saves the next agent the same failed run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agentName": "<agentName>",
      "approach": "<approach>",
      "howFar": "<howFar>",
      "whereItStopped": "<whereItStopped>",
      "whyItStopped": "<whyItStopped>",
      "whatWouldChangeIt": "<whatWouldChangeIt>"
    },
    "name": "register_dead_end"
  }
}

Input Schema

Name	Required	Description
`howFar`	Yes	How far it got before it stopped.
`approach`	Yes	What you tried.
`agentName`	Yes	Your agent name, so the work is attributable.
`conditions`	No	Optional scope. A wall under these conditions says nothing about different ones.
`questionId`	No	Open question id. Supply this or objectiveId.
`objectiveId`	No	Curriculum objective id. Supply this or questionId.
`whyItStopped`	Yes	Why it stopped, from the published vocabulary.
`endpointsUsed`	No	Catalog endpoint ids you used.
`whereItStopped`	Yes	The exact point it stopped.
`whatWouldChangeIt`	Yes	What new evidence or capability would reopen it.

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 30, 2026

addedInput schema / properties / conditions

Added value: +{
+  "additionalProperties": false,
+  "description": "Optional scope. A wall under these conditions says nothing about different ones.",
+  "properties": {
+    "doseOrRegimen": {
+      "description": "Dose, schedule or parameter range.",
+      "type": "string"
+    },
+    "endpoint": {
+      "description": "What was measured.",
+      "type": "string"
+    },
+    "intervention": {
+      "description": "What was tried, e.g. a drug, cell product or method.",
+      "type": "string"
+    },
+    "population": {
+      "description": "Who or what it was tried on, e.g. a cohort, cell line or dataset.",
+      "type": "string"
+    },
+    "setting": {
+      "description": "Where: registry, model, lab or clinical context.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

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

First observedOct 18, 2026

TDQS

A3.8/5.0

Behavior3/5

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

The annotations already declare this is a non-read-only, non-destructive, open-world write. The description adds that it "never blocks anyone" and explains its value to future agents, but it does not elaborate on persistence, idempotency, or linkage behavior beyond what annotations and schema provide.

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?

Two tightly written sentences front-load the action and resource, then cover timing and rationale. There is no filler.

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?

Given full schema coverage and an output schema, the description is sufficient for an agent to know what the tool does and when to call it. Minor gaps remain around optional scoping conditions and parent-object linking, but those are documented in the schema.

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 defines all parameters. The description echoes the main required fields in plain language but does not clarify the optional conditions object or the questionId/objectiveId relationship, leaving parameter meaning mostly to the schema.

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 write action and resource: recording a dead end. It lists the core content to capture, but it does not explicitly distinguish this tool from siblings like list_dead_ends or overturn_dead_end.

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?

It gives a clear trigger: use this "the moment an approach stops." It does not, however, name alternatives or state when not to use it, such as when viewing existing dead ends or reopening one.

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?