The Cure Protocol

get_abstraction_graph

Read-only

CALL THIS BEFORE PLANNING A MULTI-STEP QUERY. Returns the primitives this platform resolves (condition, trial, registration, identifier, phase, sponsor, modality, molecular target, literature, evidence gap, signal), the crossings between them and which endpoint performs each, plus a fidelity for every node and edge: resolved means stored and keyed, derived means reconstructed at read time and a judgement you own, absent means named by the manifesto and not held here. Optional arguments narrow it to one node or one fidelity. NEXT: get_research_curriculum for what to do with it.

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

Input Schema

Name	Required	Description	Default
`node`	No	Return one primitive and its crossings.
`fidelity`	No	resolved, derived or absent.

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 / fidelity / maxLength
```
Added value: +20000
```
- addedInput schema / properties / node / 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?

Annotations only declare readOnlyHint and openWorldHint; the description adds the crucial epistemic layer — resolved = stored and keyed, derived = reconstructed at read time and 'a judgement you own', absent = named but not held. That tells the agent how much to trust each result, which no structured field conveys.

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 imperative trigger and the NEXT pointer are correctly front- and back-loaded, and every clause carries information. It is a long run-on chain of clauses, though, which costs a little scannability.

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?

With an output schema present, the description needn't explain return shape; it supplies the trigger, the payload semantics, the fidelity vocabulary, the filtering behavior, and the follow-up tool. Nothing needed to call it correctly 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%, so both parameters are already documented, including the three fidelity values. The description only restates that the args 'narrow it to one node or one fidelity' — helpful orientation but no new semantics (e.g., whether node accepts free text or canonical names). Baseline 3 is correct.

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+resource and enumerates exactly what the graph contains (primitives, crossings, performing endpoints, per-node/edge fidelity). No sibling tool returns this structure, and the enum-like list of primitives makes the scope unmistakable.

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?

Front-loads an explicit trigger — 'CALL THIS BEFORE PLANNING A MULTI-STEP QUERY' — and routes the agent to get_research_curriculum as the next step. It lacks an explicit 'do not call when' condition (e.g., single-lookup queries should go straight to get_gene or get_disease_dossier), which keeps it short of a 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?