F
license-
qualityD
maintenanceAnalyzes clinical trial site feasibility, enrollment velocity, eligibility criteria, and benchmark performance across ClinicalTrials.gov's registry via a structured MCP interface.
trial-overdue
Server Details
Find clinical trials overdue on legally required results reporting, by sponsor and trial.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.3/5.0
Tool DescriptionsA
Average 4.3/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
With only one tool, there is no possibility of confusion between tools. The tool's purpose is clearly described and distinct by default.
Naming Consistency5/5
A single tool cannot exhibit inconsistency. The name 'overdue_trials' follows a descriptive adjective_noun pattern, which is clear and predictable.
Tool Count3/5
The server has a narrow purpose (finding overdue trials), so one tool is borderline appropriate. While minimal, it covers the primary use case, but a few additional tools (e.g., for listing sponsors or retrieving trial details) could enhance the scope.
Completeness4/5
The tool adequately covers the core function of querying overdue trials by sponsor or ticker. However, it lacks filtering by other criteria (e.g., trial status, date range) or the ability to retrieve individual trial details, which are minor gaps.
Available Tools
1 tooloverdue_trialsAInspect
Find clinical trials whose results are overdue under FDAAA 801 / 42 CFR Part 11 (results due within 1 year of primary completion). Filter by sponsor name or stock ticker. Returns public-record facts from ClinicalTrials.gov — NOT a finding of violation or legal/investment advice.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ticker | No | Stock ticker, e.g. 'BAYRY' | |
| minDays | No | Minimum days overdue | |
| sponsor | No | Sponsor company name (partial match), e.g. 'Novartis' |
Tool Definition Quality
A4.3/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries the full burden. It discloses that results are from ClinicalTrials.gov and are public-record facts, not a finding of violation. For a read-only lookup tool, this is sufficient and honest.
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?
Two sentences pack the core purpose, regulatory context, filters, and disclaimer. No wasted words; front-loaded with the key action.
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 no output schema, the description explains the return type (public-record facts) and what it is not. All three parameters are optional and explained in schema; the description adds the regulatory context. Sufficient for an agent to use correctly.
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%, so parameters are already described in the schema. The description adds context about the regulatory basis and the meaning of 'overdue', but does not add new details for individual parameters beyond what the schema provides.
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 finds overdue clinical trials under specific regulations, specifies filters, and distinguishes itself from legal advice. It uses a specific verb ('Find') and resource ('clinical trials'), leaving no ambiguity.
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?
The description explicitly states when to use the tool (to find overdue trials) and how to filter (by sponsor name or ticker). It also clarifies what the tool does NOT provide (legal or investment advice). No alternative tools exist to compare, but the guidance is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityDmaintenanceProvides access to the ClinicalTrials.gov AACT database, enabling analysis of clinical trial data, tracking development trends, and generating therapeutic landscape insights.18MIT
- AlicenseBqualityDmaintenanceProvides programmatic access to ClinicalTrials.gov API with 18 specialized tools for searching, analyzing, and retrieving detailed information about 400,000+ clinical trials worldwide, including filtering by condition, location, phase, sponsor, eligibility criteria, and outcomes.17133MIT
- Flicense-qualityDmaintenanceEnables searching and retrieving information from the ClinicalTrials.gov database of over 400,000 clinical studies, including trial details, eligibility criteria, locations, and results across 220+ countries.5