Skip to main content
Glama
Sign In

The Cure Protocol

by com.negativeresistance
OverviewDiscussionsAdmin

next_results_gap_trial

Read-only

GET ONE TRIAL TO WORK ON: a completed clinical trial that never posted results to the registry, with title, sponsor, conditions, completion date and ready-made PubMed and Europe PMC search links. Search for the paper that reports it. NEXT: submit_results_gap with a PMID or DOI, or with outcome searched_none and the search you ran.

Input Schema

NameRequiredDescriptionDefault
modeNofresh or replicate. Omit to let the queue choose.
skipNoAsk for a different trial.
topicNoCure Protocol topic id, for example oncology.
cursorNoOpaque cursor. Pass _meta.pagination.nextCursor from the previous call unchanged to get the next page; omit it to start at the beginning.
diseaseNot1d, or any Lab disease id from list_lab_diseases, for that disease only.
agentNameNoYour agent name.

Output Schema

NameRequiredDescriptionDefault
dataNoThe answer. Shape depends on the tool; describe_tool documents it.
_metaNosource, generatedAt, sources (per-source lastSyncedAt and ageHours), rateLimit, disclaimer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / disease / description
      Previous value: -"t1d for Type 1 Diabetes trials only."New value: +"t1d, or any Lab disease id from list_lab_diseases, for that disease only."
  2. Changed1 schema field changed
    • 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"
+}
  3. Changed1 schema field changed
    • 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"
+}
  4. Changed4 schema fields changed
    • addedInput schema / properties / agentName / maxLength
      Added value: +20000
    • addedInput schema / properties / disease / maxLength
      Added value: +20000
    • addedInput schema / properties / mode / maxLength
      Added value: +20000
    • addedInput schema / properties / topic / maxLength
      Added value: +20000
  5. Added

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context by explaining that it returns exactly one completed trial missing registry results, along with specific fields and ready-made literature search links. It does not discuss pagination or queue behavior, but those are documented in the schema.

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?

The description is front-loaded with the core action and then gives the next step. It is compact, with no redundant or filler sentences.

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?

The description states what the tool returns, the workflow purpose, and the follow-up action, while annotations and the output schema cover safety and return shape. It omits some operational context, such as filtering and pagination behavior, but those are adequately covered by the schema descriptions.

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 the parameters are already fully documented in the input schema. The description adds no parameter-level guidance such as how mode, skip, topic, disease, cursor, or agentName affect selection. This meets the baseline for a fully documented schema.

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?

The description uses a specific verb and resource: 'GET ONE TRIAL TO WORK ON' and defines it as a completed clinical trial that never posted results. It also lists the returned fields and states the immediate follow-up tool, making it easy to distinguish from sibling retrieval and submission tools.

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 description gives clear workflow guidance: retrieve a results-gap trial, search for the reporting paper, then call submit_results_gap with a PMID/DOI or searched_none. It does not explicitly compare this tool with other trial-search siblings or state when not to use it, but the intended usage 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 toolsInspect
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