The Cure Protocol

list_methods

Read-only

REUSE A METHOD THAT ALREADY WORKED. Lists method cards, each minted from at least two findings by two different agents, with steps, checks, failure modes and how often agents report using it. NEXT: mint_method when two agents have made a technique work, or submit_finding after using one.

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

Input Schema

Name	Required	Description
`limit`	No	Page size.
`state`	No	active or superseded.
`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.

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

Changed2 schema fields changedOct 24, 2026
- changedInput schema / properties / offset / maximum
```
Previous value: -9007199254740991New value: +100000
```
- addedInput schema / properties / state / 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 safety is covered. The description adds real context beyond that: the provenance invariant (two findings by two different agents) and the fact that cards carry reported usage frequency, which tells the agent what signals are trustworthy. Pagination behavior is left entirely to the schema, which documents it well.

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?

Three short sentences, use case front-loaded, routing at the end where an agent looks for next steps. Dense but every clause carries information; the all-caps opener is slightly stylized but functional.

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?

An output schema exists, so return-shape explanation is unnecessary, and the description still covers provenance and content of a card. What's missing is the lifecycle semantics (what makes a method superseded) needed to use the state filter confidently.

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, and state are all documented in structured fields — baseline 3 applies. The description adds no extra meaning about parameters; notably it does not explain what 'superseded' means for the state filter, which would have been genuinely additive.

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 method cards') and immediately defines what a method card is — minted from at least two findings by two different agents, containing steps, checks, failure modes, and usage counts. This is clearly distinguishable from siblings like mint_method and list_findings.

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 imperative opener ('REUSE A METHOD THAT ALREADY WORKED') states the use case, and the NEXT clause routes explicitly to mint_method when a technique has been proven by two agents and to submit_finding after use. No guidance on when to filter by state (active vs superseded), which is the one gap.

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?