The Cure Protocol

get_disease_targets

Read-only

LIST GENES ASSOCIATED WITH A DISEASE DOMAIN from Open Targets, with the source association score verbatim (not a protocol ranking) and links to evidence. NEXT: get_gene for identity and disease links, get_pathways for mechanism context.

Input Schema

Name	Required	Description
`id`	Yes	Domain id, e.g. endocrinology.
`page`	No	Page number.
`limit`	No	Results per call (the same as pageSize).
`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.
`pageSize`	No	Rows per page.
`ontologyId`	No	One of the domain's mapped ontology ids.

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.

Changed2 schema fields 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"
+}

addedInput schema / properties / limit

Added value: +{
+  "description": "Results per call (the same as pageSize).",
+  "maximum": 50,
+  "minimum": 1,
+  "type": "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 / id / maxLength
```
Added value: +20000
```
- addedInput schema / properties / ontologyId / maxLength
```
Added value: +20000
```
AddedOct 20, 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 and openWorldHint, so the safety profile is covered. The description adds real behavioral context that annotations cannot: scores are returned 'verbatim (not a protocol ranking)' and evidence links accompany them, which tells the agent how to interpret the output.

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?

Two compact sentences, front-loaded with the core action and followed immediately by routing. The all-caps emphasis is slightly blunt but costs no space; nothing extraneous is included.

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 values need not be described, and parameters are fully covered by the schema. What remains is only a minor gap: no mention of result size or what the evidence links point to.

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 cursor/pagination semantics are fully spelled out in the schema itself. The description adds nothing beyond the schema for the six parameters — 'disease domain' only loosely maps to the required id — so baseline 3 applies.

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 ('LIST GENES ASSOCIATED WITH A DISEASE DOMAIN') plus the data source (Open Targets), and the capitalized phrasing makes the scope unmistakable. It is clearly distinguishable from siblings like get_disease_drugs and get_target_evidence.

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 'NEXT: get_gene ... get_pathways ...' clause gives explicit follow-on routing, which is genuine usage guidance. It does not, however, say when to prefer this over close alternatives such as get_target_evidence or get_disease_dossier, so exclusions are missing.

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?