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.
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.
Tool Definition Quality
Average 4/5 across 1 of 1 tools scored.
Only one tool exists, so there is no risk of confusion with other tools. The tool's purpose is clearly defined and distinct.
With a single tool, naming is trivially consistent. The name 'overdue_trials' follows a clear noun_verb pattern.
One tool is slightly below the typical well-scoped count of 3-15, but it is reasonable for a very narrow domain (filtering overdue trials).
The tool covers the primary use case of finding overdue trials with filtering. Minor gaps exist (e.g., no separate tool for detailed trial info), but the core functionality is complete.
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.
| 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
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It discloses the source (ClinicalTrials.gov) and the disclaimer, but does not explicitly state read-only nature or other behavioral details like pagination or result format.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with main purpose and then caveat. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple query tool with 3 parameters and no siblings or output schema, the description provides enough context: what it finds, regulation basis, filters, and a legal disclaimer. Could be more detailed on result handling.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so baseline is 3. The description adds context by stating filters by sponsor or ticker, but does not add significant meaning beyond the schema descriptions for the parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool finds clinical trials overdue under specific regulations and filters by sponsor or ticker. It is specific and unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explains what the tool does and includes a disclaimer about not being legal advice, setting expectations. However, no alternative tools are mentioned since no siblings exist.
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!