Skip to main content
Glama

Opentargets

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.3/5.0
Behavior4/5

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

Annotations provide readOnly, idempotent, and destructive hints, and the description adds meaningful context: OAuth requirement, phone verification for SMS, 10/day SMS cap, and the always-on feed. No contradictions; the additional details go beyond the annotations.

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 dense but every sentence carries value — covering purpose, auth, types, and delivery. It is front-loaded with the core action and return value, though the length is near the upper bound for a tool description.

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?

The description is largely complete for a subscription-creation tool: it covers return value, auth, supported types with examples, feed and email/SMS channels, and SMS limitations. It omits the webhook delivery channel (present in schema), but the schema covers that, so the omission is minor.

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

Parameters4/5

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

Schema covers 100% of parameters with detailed descriptions, and the description augments this with concrete examples (e.g., items:['5.02'] = officer change, topic:'fed', series_id:'UNRATE'). This adds semantic richness beyond the schema's generic type descriptions.

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 opens with a specific verb+resource statement: 'Create a proactive monitoring subscription to a live-data event stream.' It also states it returns the new subscription id, clearly distinguishing it from sibling tools like list_subscriptions and unsubscribe.

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 provides clear context: requires a Pipeworx OAuth account, excludes anonymous and BYO users, and explains how to pull alerts from the always-on feed. It doesn't explicitly name alternatives like 'use list_subscriptions to manage existing subscriptions,' but the usage context is well implied.

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

All Opentargets 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.9/5.0
Disambiguation2/5

Several clusters of tools overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all answer data questions; entity_profile, compare_entities, and recent_changes all pull company data; polymarket_edges, polymarket_arbitrage, and bet_research all analyze prediction markets. Though descriptions are detailed, the boundaries are subtle and the beta variant is nearly identical to the stable one.

Naming Consistency3/5

Most names are snake_case, but there's no consistent verb_noun pattern: some are bare nouns (disease, target, drug, search), some are verb phrases (resolve_entity, validate_claim, generate_llms_txt), and some are domain-prefixed (ask_pipeworx_*, polymarket_*, target_*). The mixed conventions make it hard to predict tool names.

Tool Count2/5

38 tools is far beyond the typical well-scoped server, and the set mixes Open Targets lookup, a general data platform (Pipeworx), prediction markets, npm package checks, and AI-marketing utilities under the name 'Opentargets'. Many tools are unrelated to the server's apparent core purpose.

Completeness4/5

The Open Targets drug-discovery workflow is well covered: search for IDs, get disease/drug/target profiles, and get associations/known drugs. However, the broader platform lacks some lifecycle operations (no create/update/delete since it's read-only), and the unrelated utilities (generate_llms_txt, scan_dependency) appear tacked on rather than filling domain gaps.

Resources