Skip to main content
Glama
@corridordata/mcp-server

@corridordata/mcp-server

Official
by corridordata

search_clinical_trial_sponsors

Read-onlyIdempotent

Find commercial biotech, pharma, and medtech sponsors running Phase 1–4 clinical trials via ClinicalTrials.gov, with central contact emails, phones, and domains.

Instructions

Find commercial biotech, pharma, and medtech companies running Phase 1–4 clinical trials via ClinicalTrials.gov v2 API with central study contact emails, phones, and company domains (corridordata/clinicaltrials-biotech-sponsor-leads).

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": "search_clinical_trial_sponsors"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxItemsNoMaximum clinical trial sponsor leads to return.
statusesNoTrial recruitment statuses to include.
maxTotalChargeUsdNoOptional per-run USD spend cap forwarded to Apify Pay-Per-Event billing (`maxTotalChargeUsd`).
conditionOrKeywordNoDisease, therapeutic area, or drug modality (e.g. 'oncology', 'GLP-1', 'CAR-T').
industrySponsorsOnlyNoRestrict to commercial biotech/pharma/medtech sponsors (exclude universities/NIH).
withContactEmailOnlyNoOnly return trials listing a direct central contact email.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds meaningful context beyond that: the upstream data source is the ClinicalTrials.gov v2 API, the actor slug is given, and the results include central contact emails, phones, and company domains — implying contact data is present but not guaranteed. It says nothing about cost per item, latency, or result freshness.

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?

A single front-loaded sentence with no filler; the verb and target resource come first and the supporting details follow. It is dense — API version and an actor slug are packed into one clause — but every clause carries information, and there is no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With six optional parameters, no output schema, and no annotations covering results, the description should sketch the response shape. It names three output fields (emails, phones, domains) but does not say whether results are one row per trial or per sponsor, how many fields each lead carries, or anything about pagination beyond maxItems. Adequate to call the tool, incomplete to predict what comes back.

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 every one of the six parameters is already documented in the schema, making 3 the baseline. The description adds only marginal meaning by echoing the contact-email and commercial-sponsor filters that correspond to withContactEmailOnly and industrySponsorsOnly; it adds no format or interaction guidance for maxItems, statuses, or maxTotalChargeUsd.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb ("Find"), precisely bounded resource (commercial biotech/pharma/medtech companies running Phase 1–4 clinical trials), plus the data source (ClinicalTrials.gov v2 API). The domain is clearly disjoint from the sibling tools (jobs, grants, tenders, SEC filings), but the description never explicitly contrasts with an alternative, so it stops short of the top band.

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

Usage Guidelines3/5

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

No explicit when-to-use or when-not-to-use statement and no named alternative. Usage is only implied by the framing: it is for assembling sponsor lead lists with contact data, and industrySponsorsOnly defaults to true, which signals the primary commercial-lead use case. An agent must infer selection criteria rather than read them.

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