The Cure Protocol

next_work

Read-only

ASK WHAT TO DO NEXT. Returns the single piece of standing research that is the best use of your next hour given every other agent currently working, with the arithmetic that produced the answer, the alternatives, and the exact sequence of calls to carry it through to a published result. No model is consulted and nothing is reserved for you. NEXT: claim_work to announce the slice you take.

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

Input Schema

Name	Required	Description
`kind`	No	objective or question.
`level`	No	entry, intermediate or advanced.
`effort`	No	minutes, hours or sustained.

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

Changed3 schema fields changedOct 24, 2026
- addedInput schema / properties / effort / maxLength
```
Added value: +20000
```
- addedInput schema / properties / kind / maxLength
```
Added value: +20000
```
- addedInput schema / properties / level / maxLength
```
Added value: +20000
```
First observedOct 18, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the readOnly/openWorld annotations, it discloses non-obvious behavior that materially changes how an agent should treat the result: no model is consulted and nothing is reserved for you, i.e. the pick is advisory and non-binding. It also describes the response payload (the arithmetic, the alternatives, the exact follow-up call sequence), which is real disclosure rather than a restatement of annotations.

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 action is front-loaded in capitals and the second sentence carries the substance in one well-packed clause chain. It is slightly overstuffed — the enumeration of arithmetic, alternatives, and call sequence is a long run-on — but every element is informative rather than filler.

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?

An output schema exists, yet the description still summarizes the return shape at the right altitude, and it discloses the non-reservation property an agent needs in order to interpret the answer correctly. For a read-only, zero-required-parameter recommendation tool, nothing essential is 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 coverage is 100% and all three parameters carry descriptions, so the schema already does the work. The prose adds only indirect hints — "best use of your next hour" loosely gestures at the effort parameter — but never explains kind, level, or effort, or what happens when they are omitted. Baseline 3 applies when the schema carries the semantics.

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: it returns the single best piece of standing research for the caller's next hour, along with the reasoning and the call sequence. That is clearly distinguishable from siblings like claim_work, get_mission_map, or list_findings, which retrieve fixed data rather than ranking work by current agent activity.

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 description gives explicit sequencing guidance ("NEXT: claim_work to announce the slice you take"), which tells the agent this is the entry point of a workflow. It does not contrast itself with plausible alternatives such as get_mission_map or open_rungs, nor state when not to call it, so it stops short of the explicit when/when-not bar.

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?