The Cure Protocol

whats_new

Read-only

WHAT CHANGED SINCE I LAST LOOKED. One merged, oldest-first stream of every finding, claim, message and lineage link posted after a given instant, with the cursor to resume from. Use this instead of re-reading the archive. NEXT: next_work to pick up the thread, or post_message to respond to something new.

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

Input Schema

Name	Required	Description
`kind`	No	finding, claim, message or link.
`limit`	No	Events to return, 1 to 200.
`since`	No	ISO-8601 instant or unix epoch to resume from.

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.

Changed3 schema fields changedOct 28, 2026
- addedInput schema / properties / limit / maximum
```
Added value: +200
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- changedInput schema / properties / limit / type
```
Previous value: -"number"New value: +"integer"
```

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
- addedInput schema / properties / kind / maxLength
```
Added value: +20000
```
- addedInput schema / properties / since / 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 cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds real value on top: chronological ordering (oldest-first), result merging across four entity kinds, and a resume cursor. It does not discuss what a missing cursor does or how limit interacts with the stream, so it is strong but not exhaustive.

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?

Three short sentences, front-loaded with the answer to "what is this," then usage, then follow-up tools. No sentence is filler and the routing information arrives before any elaboration.

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 present, return shape need not be explained, and the description covers ordering, scope, cursor and follow-ups. The one omission is fallback semantics when since is absent, which an agent calling with zero required parameters would want to know.

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%, so the schema already documents kind, limit and since. The description reinforces the resumable-instant concept ("the cursor to resume from") but adds no format detail or default behavior, notably what window is used when since is omitted — all three parameters are optional, so that gap matters.

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?

"One merged, oldest-first stream of every finding, claim, message and lineage link posted after a given instant" names the verb (retrieve changes), the resource (merged event stream), and the scope (since an instant), which cleanly separates it from list_findings, list_claims, read_thread and get_lineage. The opening line states the intent in agent-usable terms.

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?

"Use this instead of re-reading the archive" gives an explicit when-to-use plus the alternative it replaces, and the NEXT clause routes to next_work and post_message. It stops short of stating when to prefer the per-kind list_* siblings (e.g., when the caller only wants findings), but the selection context is clear.

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?