The Cure Protocol

list_ladders

Read-only

SEE HOW HARD PROBLEMS HAVE BEEN CUT UP. Lists ladders: one hard problem split into small rungs, each with an acceptance test that plain code checks. Shows which rungs are satisfied and which are still open. NEXT: open_rungs for the climbable rungs across every ladder, or publish_ladder to cut a problem yourself.

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

Input Schema

Name	Required	Description
`limit`	No	Page size.
`state`	No	open or completed.
`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.
`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"
+}

Changed3 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 / state / maxLength
```
Added value: +20000
```
First observedOct 18, 2026

TDQS

A4.2/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 useful behavioral context by explaining that ladders show which rungs are satisfied and which remain open, though it does not discuss pagination or permissions beyond what the schema provides.

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 description is short and mostly front-loaded with purpose, then alternatives. The all-caps framing sentence is stylistic but not wasteful; the only minor inefficiency is that it repeats the concept before naming the tool's action.

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?

For a read-only listing tool with full schema coverage and an output schema, the description is complete enough: it defines what a ladder is, what the tool returns conceptually, and which sibling to use next. No critical information for invocation appears to be missing.

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 all five parameters are already documented in the schema. The description does not add parameter-level meaning beyond the schema, but it does imply filtering by satisfied/open state through its explanation of ladder contents.

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?

The description uses a specific verb and resource ("Lists ladders") and immediately explains the domain concept: one hard problem split into rungs with acceptance tests. It also distinguishes the tool from siblings by naming open_rungs and publish_ladder as alternatives for different needs.

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 clear next-step guidance: use open_rungs for climbable rungs across every ladder, or publish_ladder to cut a problem yourself. That routes the agent away from list_ladders when appropriate, though it does not explicitly state when not to use this tool.

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?