Clinicaltrials

Ct Sponsor Trials

ct_sponsor_trials

Read-onlyIdempotent

List the trials a company LEADS on ClinicalTrials.gov, by sponsor or organization name. Returns status, phase, and conditions to map a research pipeline. Matches the registered lead-sponsor field, so trials another organisation runs using the company's drug are excluded unless sponsor_match asks for them.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Number of results (1-100, default 20)
`phase`	No	Optional phase filter
`status`	No	Optional status filter
`sponsor`	Yes	Sponsor or company name (e.g., "Pfizer", "Novo Nordisk", "Moderna"). Matched against the registered LEAD sponsor by default.
`sponsor_match`	No	Which sponsor role the name must fill. "lead" (the default) returns only trials whose registered LEAD sponsor is that company. "lead_or_collaborator" also returns trials led by someone else that list the company as a collaborator — typically academic trials of the company's drug. Every returned study carries sponsor_match_field naming which one matched.

Output Schema

TableJSON Schema

Name	Required	Description
`sponsor`	Yes	Sponsor name queried
`studies`	Yes	List of formatted trial summaries
`total_count`	Yes	Total trials by sponsor

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedAug 29, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "limit": 25,
-    "sponsor": "Pfizer"
-  },
-  {
-    "phase": "PHASE4",
-    "sponsor": "Novo Nordisk",
-    "status": "COMPLETED"
-  }
-]New value: +[
+  {
+    "limit": 25,
+    "sponsor": "Pfizer"
+  },
+  {
+    "phase": "PHASE4",
+    "sponsor": "Novo Nordisk",
+    "status": "COMPLETED"
+  },
+  {
+    "limit": 6,
+    "sponsor": "Merck Sharp & Dohme LLC",
+    "sponsor_match": "lead_or_collaborator"
+  }
+]

changedInput schema / properties / sponsor / description

Previous value: -"Sponsor or company name (e.g., \"Pfizer\", \"Novo Nordisk\", \"Moderna\")"New value: +"Sponsor or company name (e.g., \"Pfizer\", \"Novo Nordisk\", \"Moderna\"). Matched against the registered LEAD sponsor by default."

addedInput schema / properties / sponsor_match

Added value: +{
+  "description": "Which sponsor role the name must fill. \"lead\" (the default) returns only trials whose registered LEAD sponsor is that company. \"lead_or_collaborator\" also returns trials led by someone else that list the company as a collaborator — typically academic trials of the company's drug. Every returned study carries sponsor_match_field naming which one matched.",
+  "enum": [
+    "lead",
+    "lead_or_collaborator"
+  ],
+  "type": "string"
+}

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "sponsor": {
+      "description": "Sponsor name queried",
+      "type": "string"
+    },
+    "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 trials by sponsor",
+      "type": "number"
+    }
+  },
+  "required": [
+    "sponsor",
+    "total_count",
+    "studies"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "limit": 25,
+    "sponsor": "Pfizer"
+  },
+  {
+    "phase": "PHASE4",
+    "sponsor": "Novo Nordisk",
+    "status": "COMPLETED"
+  }
+]

First observedApr 22, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare the operation safe/read-only/idempotent, so the description adds useful behavior beyond them: matching is against the registered LEAD sponsor, collaborator trials are excluded by default, and sponsor_match_field indicates which role matched. This is meaningful, non-obvious behavior.

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?

Three sentences, each earning its place: action/target, output/purpose, and the critical edge-case behavior. It is front-loaded and concise without omitting needed nuance.

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?

With 5 parameters, output schema present, and strong annotations, the description covers purpose, output fields, and the most important matching edge case. It lacks explicit alternative-routing or pagination/rate details, but those are secondary to correct invocation for this tool.

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 schema already documents all parameters, defaults, and enum choices. The narrative description adds context around sponsor_match's inclusion/exclusion behavior but doesn't need to compensate for schema gaps.

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 states a specific action ('List'), a resource ('trials a company LEADS on ClinicalTrials.gov'), and the key scope (registered lead-sponsor field). It clearly distinguishes this from generalized trial search or collaborator-focused 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?

It gives clear context: use to map a company's research pipeline by lead-sponsor status/phase/conditions, and it explicitly notes the exclusion of collaborator-run trials unless sponsor_match asks. It doesn't name sibling alternatives explicitly, but the matching-behavior guidance is strong.

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.