Skip to main content
Glama

SBOM Dependency CVE & US CISA Known Exploited Vulnerability MCP

Track Live ClinicalTrials.gov Biotech & MedTech Pipelines

track_biotech_clinical_trials
Read-onlyIdempotent

Queries ClinicalTrials.gov API v2 for active Phase 1-3 trials, sponsors, NCT IDs, and completion dates.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "track_biotech_clinical_trials"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesDisease, drug target, or sponsor name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety behavior is covered. The description adds that it hits an external public API (v2) and applies an 'active Phase 1-3' filter, plus which fields come back, but says nothing about result caps, pagination, or rate limits.

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?

One sentence, front-loaded with the verb and data source, with zero filler or repetition of the title.

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?

For a one-parameter, read-only lookup with no output schema, the definition covers the source, the eligibility filter, and the key returned fields, which is enough to invoke it correctly. Only the absence of any result-size or pagination note keeps it short of full completeness.

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 coverage is 100% and the single 'query' parameter is already documented as 'Disease, drug target, or sponsor name'. The description adds no syntax, matching behavior, or formatting guidance beyond the schema, so the baseline 3 applies.

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?

The description names a specific verb (Queries) and a specific resource (ClinicalTrials.gov API v2), then scopes it to 'active Phase 1-3 trials' and lists the data points returned (sponsors, NCT IDs, completion dates). It is clearly distinct from the CVE-audit and prior-art siblings, though it never explicitly contrasts with them.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance; the agent must infer from the title 'Track Live ... Pipelines' and the Phase 1-3 filter that this is the tool for current pipeline research. No alternative or precondition is mentioned.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.