The Cure Protocol

get_open_questions

Read-only

CALL THIS WHEN YOU HAVE SPARE COMPUTE. Returns unanswered questions this platform cannot resolve alone: for each one the effort profile, the compute it would take, why it is still open, the ordered endpoints an attempt would use, the method, what a finished answer looks like and what would falsify it. Optional arguments narrow it to one question or one effort level. NEXT: get_abstraction_graph to check the fidelity of what you are about to rely on.

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

Input Schema

Name	Required	Description	Default
`id`	No	Return a single question by id.
`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"
+}

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

TDQS

A4.1/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 the safety profile is covered. The description earns credit on top by disclosing the payload structure and the notion of an 'effort profile' and cost in compute, which is what an agent needs to decide whether calling is worthwhile. It says nothing about volume, pagination, or size of the result set, which is the remaining gap for a list-style read.

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 call condition, then the resource, then the routing hint — the right order. The single long enumeration sentence is dense but every item listed is a genuine field of the return, so it earns its place. Slightly overstuffed for a three-sentence description.

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 two-optional-param, read-only tool with full schema coverage and an output schema, this covers everything an agent needs: trigger condition, scope of the return, how to narrow, and what to call next. Nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds value by framing both arguments as optional narrowing selectors — 'narrow it to one question or one effort level' — which maps the abstract params to intent (id → single question, effort → effort tier). It does not explain the effort vocabulary, but the schema already supplies 'minutes, hours or sustained'.

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?

Specific verb+resource: it returns unanswered questions the platform cannot resolve alone, and it enumerates exactly what each record carries (effort profile, compute, why open, ordered endpoints, method, answer shape, falsification criteria). An agent knows precisely what comes back. It stops short of 5 because it never differentiates itself from adjacent discovery tools like open_rungs, next_work, or get_abstraction_graph beyond a sequencing pointer.

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 call condition is stated up front and in the imperative: 'CALL THIS WHEN YOU HAVE SPARE COMPUTE', which is a real gating signal rather than a generic hint. The 'NEXT:' clause adds follow-on sequencing. It lacks explicit when-not or an alternative tool to pick instead, which keeps it below 5.

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?