Skip to main content
Glama

Bioregistry

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?

The description adds significant behavioral context beyond the annotations. It discloses that creation requires an authenticated account, details the idempotent behavior (though not explicit, the annotation is supported by the subscription nature), and specifies constraints like the SMS daily cap and webhook auto-disable after failures. No contradictions with annotations are observed.

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 well-structured, starting with the core purpose and return value, then detailing types and delivery. It packs a lot of information into one paragraph, which could benefit from bullet points for readability, but it remains clear without wasting words.

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 the tool's complexity (3 parameters, nested objects, many enums, no output schema), the description is remarkably complete. It covers all subscription types, their parameters, delivery channels with constraints, account requirements, and the return value (new subscription id). No important aspect is missing.

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?

With 100% schema coverage, the schema already documents all parameters. The description enriches this by providing type-specific examples for params (e.g., sec_8k requires ticker and items) and detailed delivery options (e.g., webhook requires HTTPS and HMAC verification). This adds practical meaning beyond the schema definitions.

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's purpose: 'Create a proactive monitoring subscription to a live-data event stream.' It specifies the verb (Create), resource (subscription to event stream), and provides examples of supported types, 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 explains when to use the tool (requires a Pipeworx OAuth account, anonymous/BYO cannot persist subscriptions) and details the supported subscription types and their specific parameters. It also outlines delivery channel constraints (SMS cap, webhook auto-disable). Some guidance on alternatives (e.g., using recent_alerts for the feed) could be more explicit, but overall it provides clear usage context.

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

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

Severe overlap exists between ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research, all of which route to the same 5,743-tool catalog with only subtle differences. The pair resolve (CURIE-to-URL) and resolve_entity (name-to-ID) share the same verb but mean completely different things in different domains, and the five polymarket tools have heavily overlapping purposes.

Naming Consistency2/5

The set mixes multiple conventions: noun-only names (prefix, prefixes, search, resolve), verb_noun names (generate_llms_txt, scan_dependency, validate_claim), adjective_noun names (recent_alerts, recent_changes), and vendor-prefixed names (ask_pipeworx*, pipeworx_*, polymarket_*). Some names break the pattern entirely, like forget and remember, and the plural prefix/prefixes pair is inconsistent.

Tool Count2/5

35 tools is heavy for any single server, but the bigger problem is that roughly 31 tools are Pipeworx platform utilities (asking, memory, subscriptions, feedback) while only 4 serve the stated 'Bioregistry' purpose. A server named Bioregistry carrying prediction-market arbitrage and AI-visibility tools is poorly scoped regardless of the absolute count.

Completeness2/5

The Bioregistry surface is thin: search, prefix, prefixes, and resolve cover lookup/pagination but no registry management, and the remaining tools belong to an entirely different, unrelated domain. The server's apparent purpose ('Bioregistry') is barely served, while the Pipeworx functionality, though broad, is buried under an incongruent server name, making the overall surface incomplete and incoherent.

Resources