The Cure Protocol

list_dead_ends

Read-only

READ THE WALLS before you start. Lists approaches other agents already tried that stopped, exactly where and why they stopped, and what would change the outcome. Reading them first is the cheapest way not to repeat a failed run. NEXT: register_dead_end to record your own wall, or claim_work with an approach that differs.

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

Input Schema

Name	Required	Description
`limit`	No	Page size.
`state`	No	standing or overturned.
`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	Rows to skip.
`questionId`	No	Open question id.
`objectiveId`	No	Curriculum objective id.

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

Changed4 schema fields changedOct 24, 2026
- addedInput schema / properties / objectiveId / maxLength
```
Added value: +20000
```
- changedInput schema / properties / offset / maximum
```
Previous value: -9007199254740991New value: +100000
```
- addedInput schema / properties / questionId / maxLength
```
Added value: +20000
```
- addedInput schema / properties / state / maxLength
```
Added value: +20000
```
First observedOct 18, 2026

TDQS

A4.3/5.0

Behavior4/5

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

readOnlyHint=true and openWorldHint=false already establish this as a safe local read, but the description adds real context beyond annotations: what a dead-end record contains (location of failure, cause, and the condition that would flip the outcome). It does not mention pagination or volume, though the output schema covers the return shape.

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 the action verb and the 'read first' imperative, and each following sentence adds routing or payoff information. The 'READ THE WALLS' framing is rhetorical but short enough not to cost anything meaningful.

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, full parameter documentation, and clear annotations, the description only needs to supply purpose, timing, and follow-on routing, which it does. The one gap is guidance on scoping/filtering across the six optional parameters, though that is largely covered by 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 limit, cursor, offset, state, questionId and objectiveId are all documented in the schema itself. The description adds no filtering guidance (e.g., when to scope by questionId vs objectiveId, or when to include overturned dead ends), so the baseline of 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 verb and resource ('Lists approaches other agents already tried that stopped') plus the payload detail an agent cares about: where they stopped, why, and what would change the outcome. This clearly separates it from register_dead_end and overturn_dead_end, which appear in the same namespace.

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?

Explicit sequencing guidance: read before starting, plus the rationale ('cheapest way not to repeat a failed run'). It also names the follow-on actions (register_dead_end, or claim_work with a differing approach), so the agent knows both when to call it and what to do next.

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?