Clinicaltrials

Ct Recent Updates

ct_recent_updates

Read-onlyIdempotent

Track recent ClinicalTrials.gov activity by a specific event class within a verifiable date window. Three DISTINCT recency events, chosen via date_type: "last_update" (any edit to a study, ~5k/week — the default), "first_posted" (a study newly REGISTERED, ~1.3k/week), or "results_posted" (RESULTS first posted, ~140/week). Pass since (and optional until, YYYY-MM-DD) to bound a window — e.g. the last 7 days — and the returned total_count is the exact number of studies in that window so you can verify a weekly count from the output. Every study returns all THREE dates separately (first_posted_date, last_update_post_date, results_first_post_date) plus the design fields a screen needs (study_type, primary_purpose, phase, status, enrollment, conditions, interventions, sponsor). Sorted by the chosen event date, newest first. Use for "new trials registered this week", "trials that posted results in the last month", "recently updated diabetes studies".

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Number of results per page (1-100, default 20). total_count reports the full window size regardless of limit.
`query`	No	Optional search term (condition/drug/keyword) to narrow results.
`since`	No	Window start (inclusive), YYYY-MM-DD. e.g. for a weekly review pass 7 days ago. Applies to the chosen date_type.
`until`	No	Optional window end (inclusive), YYYY-MM-DD. Omit for open-ended (up to today).
`status`	No	Optional overall-status filter (validated; e.g. RECRUITING, or a comma-union like "RECRUITING,COMPLETED").
`date_type`	No	Which recency event to track/sort/window by: "last_update" (any edit, default), "first_posted" (new registration), "results_posted" (results first posted). These are different event classes with very different volumes — pick deliberately.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`studies`	Yes	List of formatted trial summaries
`total_count`	Yes	Total recently updated trials

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedJul 24, 2026

addedInput schema / properties / date_type

Added value: +{
+  "description": "Which recency event to track/sort/window by: \"last_update\" (any edit, default), \"first_posted\" (new registration), \"results_posted\" (results first posted). These are different event classes with very different volumes — pick deliberately.",
+  "enum": [
+    "last_update",
+    "first_posted",
+    "results_posted"
+  ],
+  "type": "string"
+}

changedInput schema / properties / limit / description

Previous value: -"Number of results (1-100, default 20)"New value: +"Number of results per page (1-100, default 20). total_count reports the full window size regardless of limit."

changedInput schema / properties / query / description

Previous value: -"Optional search term to narrow results"New value: +"Optional search term (condition/drug/keyword) to narrow results."

addedInput schema / properties / since

Added value: +{
+  "description": "Window start (inclusive), YYYY-MM-DD. e.g. for a weekly review pass 7 days ago. Applies to the chosen date_type.",
+  "type": "string"
+}

addedInput schema / properties / status

Added value: +{
+  "description": "Optional overall-status filter (validated; e.g. RECRUITING, or a comma-union like \"RECRUITING,COMPLETED\").",
+  "type": "string"
+}

addedInput schema / properties / until

Added value: +{
+  "description": "Optional window end (inclusive), YYYY-MM-DD. Omit for open-ended (up to today).",
+  "type": "string"
+}

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "studies": {
+      "description": "List of formatted trial summaries",
+      "items": {
+        "properties": {
+          "collaborators": {
+            "description": "List of collaborator names",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "completion_date": {
+            "description": "Final completion date",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "conditions": {
+            "description": "List of trial conditions",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "enrollment": {
+            "description": "Target enrollment count",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "enrollment_type": {
+            "description": "Enrollment type",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "interventions": {
+            "description": "List of interventions",
+            "items": {
+              "properties": {
+                "description": {
+                  "description": "Intervention description",
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "name": {
+                  "description": "Intervention name",
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "type": {
+                  "description": "Intervention type",
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "nct_id": {
+            "description": "NCT identifier",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "official_title": {
+            "description": "Official trial title",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "phase": {
+            "description": "Trial phase(s) comma-separated",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "primary_completion_date": {
+            "description": "Primary completion date",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "sponsor": {
+            "description": "Lead sponsor name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "sponsor_class": {
+            "description": "Sponsor class",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "start_date": {
+            "description": "Trial start date",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "status": {
+            "description": "Overall trial status",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "description": "Brief trial title",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_count": {
+      "description": "Total recently updated trials",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total_count",
+    "studies"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "limit": 20,
+    "query": "oncology"
+  },
+  {
+    "limit": 30
+  }
+]

First observedApr 22, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already indicate read-only, idempotent, open-world, non-destructive behavior. Description adds details: total_count verifies exact window size, all three dates returned, sorting by chosen event date. No contradictions with annotations.

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?

Single paragraph with front-loaded purpose, logical flow from events to parameters to return structure to examples. Every sentence adds value, no redundancy or fluff. Efficiently packs substantial information.

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?

Covers all key aspects: event types, parameter usage, return fields, example scenarios. Could mention pagination or error cases, but given output schema exists and annotations are rich, the description is sufficiently complete for an AI agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema descriptions cover all 6 parameters (100% coverage). Description adds significant value: explains date_type event volumes and deliberate selection, clarifies since/until window bounding, and notes limit vs total_count distinction. Goes well beyond schema alone.

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 clearly states the tool tracks recent ClinicalTrials.gov activity by event class, with explicit distinctions between three recency events and their volumes. It differentiates itself from siblings like ct_search or ct_count_by_condition by focusing on date-windowed activity tracking.

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?

Provides concrete use cases ('new trials registered this week', 'trials that posted results in the last month') and explains when to use each date_type. Does not explicitly name sibling alternatives or state when not to use, but the examples make the context clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Clinicaltrials 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.