The Cure Protocol

get_trial_stats

Read-only

USE WHEN orienting on the trial corpus or answering a whole-index count. Returns the total source-record count, the deduplicated canonical trial count, how many are currently active, the per-registry attribution, and the curated topic ids you can pass as topic to the other trial tools. Counts are never summed across registries — each registry's contribution is reported separately alongside the distinct total. The top-level counts cover the whole index; diseaseDomains gives the unique totals for the 15 disease domains (the same figures as get_mission_map) plus how many trials match no domain, so the two always reconcile. NEXT: search_world_trials to query it, get_registry_sources for licence and sync freshness per registry.

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

Input Schema

Name	Required	Description	Default
No arguments

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

First observedOct 18, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already establish readOnly and closed-world, and the description adds non-obvious semantics: registry counts are never summed (each reported separately alongside a distinct total), and diseaseDomains figures reconcile exactly with get_mission_map. This is real interpretive context not derivable from the annotations, though a good share of the text restates return fields that the output schema already carries.

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 trigger, then the payload, then the counting caveat, then routing — good ordering with zero filler sentences. It is slightly long because the field enumeration repeats what the output schema already lists.

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?

Given an output schema, no parameters, and read-only annotations, nothing an agent needs to call this correctly is missing: it knows the trigger, the shape of the answer, the counting convention, and where to go next.

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?

Zero parameters, so baseline 4 applies. The description additionally documents the `topic` ids surfaced by this tool as valid inputs to other trial tools, which is useful cross-tool parameter context even though this tool itself takes nothing.

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?

Specific verb+resource: it returns index-wide counts (source records, deduplicated canonical trials, active count, per-registry attribution, topic ids). It distinguishes itself from neighbors by explaining the reconciliation relationship with get_mission_map and by routing to search_world_trials for queries.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Opens with an explicit trigger ("USE WHEN orienting on the trial corpus or answering a whole-index count") and closes with a NEXT clause naming the exact follow-on tools (search_world_trials, get_registry_sources) and what each is for.

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?