Skip to main content
Glama

bio-catalyst

by com.dropwatchhq

upcoming_catalysts

Return upcoming biotech/pharma catalysts (clinical-trial readouts, FDA AdComm meetings, recent approvals) VERIFIED against and linked to their official source (ClinicalTrials.gov, Federal Register, openFDA). Each record includes the official sourceUrl, the exact sourceField the date came from, and a verifiedAsOf stamp. This is scheduling/reference data, NOT investment advice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoHorizon in days from today (default 90).
kindNoFilter by event type.
limitNoMax events (default 50).
phaseNoFilter trial readouts by phase, e.g. 'PHASE3'.
tickerNoFilter to one public-company ticker.

TDQS

A3.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses that data is verified against official sources and includes sourceUrl, sourceField, and verifiedAsOf stamp. It also clarifys that it is scheduling/reference data. This is fairly transparent for a read-only query tool.

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?

The description is concise, about 4 sentences, and front-loaded with the main purpose. Each sentence adds value, but some minor redundancy (e.g., 'VERIFIED against and linked to their official source' could be slightly tighter).

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?

No output schema, but the description explains what each record includes (sourceUrl, sourceField, verifiedAsOf). It covers the main functionality well, though lacks details on pagination or date range limits beyond the days parameter.

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 baseline is 3. The description does not add additional meaning beyond the schema, but the schema already describes each parameter adequately.

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 clearly states the tool returns upcoming biotech/pharma catalysts with specific types (readouts, adcom, approvals). It emphasizes verification against official sources. However, it does not explicitly differentiate from sibling tools like catalyst_for_company or catalyst_for_drug, which are more specific.

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?

No guidance on when to use this tool versus alternatives. The disclaimer 'not investment advice' is not usage guidance. The description lacks explicit when-to-use or when-not-to-use context.

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

All bio-catalyst toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation5/5

Each tool targets a distinct query type: by company ticker, by drug name, or upcoming catalysts. Descriptions clearly differentiate them, leaving no ambiguity.

Naming Consistency4/5

Tool names follow a similar pattern using 'catalyst' as a prefix, with 'for_company', 'for_drug', and 'upcoming_' modifiers. While not strictly verb_noun, they are consistent and predictable.

Tool Count4/5

With 3 tools, the server is focused and efficient for its domain of biotech catalysts. It covers the core query types without being overly sparse or bloated.

Completeness4/5

The set covers catalysts by company, by drug, and upcoming events. Minor gaps like historical or date-range queries exist but are acceptable given the server's scope and the detailed data returned.

Resources