Skip to main content
Glama

Clinicaltrials

by io.github.pipeworx-io

Subscribe to Alerts

subscribe
Idempotent

Create a proactive monitoring subscription to a live-data event stream. Returns the new subscription id. Requires a Pipeworx OAuth account (anonymous + BYO cannot persist subscriptions). Supported types: "sec_8k" (8-K filings matching ticker + item codes — e.g. items:["5.02"] = officer change), "polymarket_edge" (Polymarket↔Kalshi cross-venue mispricings — params:{topic:"fed"}), "fred_series" (new FRED observations — params:{series_id:"UNRATE"}). Delivery channels: feed (always on — pull via recent_alerts or GET registry.pipeworx.io/alerts.json), and optionally email (set delivery:{email:"you@x.com"}) or sms (delivery:{sms:"+15551234567"} — phone must be verified at /account first; 10/day cap).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesSubscription type.
paramsYesType-specific filter. sec_8k: {ticker:"AAPL", items?:["5.02","1.01"]}. polymarket_edge: {topic:"fed", min_spread_bps?:500}. fred_series: {series_id:"UNRATE"}. patent_grant: {applicant:"Apple Inc."}. clinical_trial: {sponsor?:"Pfizer", condition?:"lung cancer", phase?:"PHASE3"} (sponsor or condition required).
deliveryNoOptional delivery channels in addition to the always-on persistent feed. {email:"you@x.com"} sends a templated alert per fired event. {sms:"+15551234567"} sends an SMS per event — must match the verified phone on the caller's account (verify at https://pipeworx.io/account first; 10/day cap). {webhook:"https://..."} POSTs each event JSON to your endpoint, HMAC-signed — the response includes delivery.webhook_secret (whsec_…) ONCE; verify X-Pipeworx-Signature = sha256 HMAC of "<X-Pipeworx-Timestamp>.<raw body>". Auto-disabled after 10 consecutive failing runs.

TDQS

A4.7/5.0
Behavior5/5

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

Adds significant behavioral details beyond annotations: account requirements, type-specific parameters, delivery channel constraints (e.g., SMS cap, webhook HMAC signing), and secret handling. Annotations already provide non-readonly, idempotent, non-destructive hints which are consistent.

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?

Well-structured and front-loaded with main purpose, then organized by type and delivery channel. Every sentence adds necessary detail without being verbose. Approximately 200 words covering all essential aspects.

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?

Very comprehensive: covers all types, delivery channels, account requirements, and returns the subscription id. However, does not clarify idempotency behavior (though hinted by annotations). Minor gap given the complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds rich meaning beyond the 100% schema coverage: explains each type's purpose with examples (e.g., sec_8k with items codes), delivery options with constraints, and type-specific params. Schema alone would be insufficient for correct usage.

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?

Clearly states 'Create a proactive monitoring subscription', which is a specific verb and resource. Distinguishes from sibling tools like list_subscriptions, unsubscribe, recent_alerts.

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?

Explains when to use (to create a subscription) and prerequisites (Pipeworx OAuth account). Implicitly distinguishes from siblings, but does not explicitly mention when not to use or name alternatives.

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

All Clinicaltrials 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.6/5.0
Disambiguation1/5

Several tools appear to do the same thing at the top level: ask_pipeworx, ask_pipeworx_beta (explicitly identical today), and ask_pipeworx_grounded are near-duplicate routing entry points, and deep_research overlaps heavily with them. Among the ct_* tools, ct_count_by_condition, ct_competitive_landscape, ct_sponsor_pipeline, and ct_compare_sponsors all provide overlapping counting/landscape functionality, making correct selection genuinely ambiguous.

Naming Consistency4/5

The overwhelming majority of tools use lowercase snake_case and mostly follow a verb_noun or domain-prefixed pattern (ct_search, ct_get_study, list_subscriptions, validate_claim, resolove_entity). Some names are noun phrases rather than verbs (ct_competitive_landscape, entity_profile, polymarket_edge_tracker) but the overall style is consistent and readable, with only minor deviations.

Tool Count2/5

44 tools is far too many for a server named 'Clinicaltrials'; only 13 tools are actually clinical-trials-specific while the rest span general data lookup, prediction markets, memory, subscriptions, and npm scanning. The count is inflated by redundant entry points (ask_pipeworx/beta/grounded) and overlapping ct tools, making the set feel heavy and unfocused.

Completeness4/5

For the clinical-trials registry domain, the surface is largely complete: search, full study details, results summaries, condition counts, sponsor pipelines, location-based lookup, recent updates, and catalyst tracking are all represented. Minor gaps exist (e.g., historical versions/protocol amendments and advanced filter combinations), but most could be worked around via the universal ask_pipeworx router.

Resources