Skip to main content
Glama

Clinicaltables

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.9/5.0
Behavior5/5

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

Discloses behavioral traits beyond annotations: OAuth requirement, type-specific parameter behaviors, SMS cap (10/day), phone verification prerequisite, webhook auto-disable after 10 failures, and signing mechanism. No contradiction with annotations (readOnlyHint=false, idempotentHint=true).

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 front-loaded with the main purpose, but is dense with information. While every sentence earns its place, readability could be improved with more structured formatting (e.g., bullet points for types). Still, no wasted 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 complexity (multiple types, delivery channels, constraints) and no output schema, the description covers all necessary aspects: return value (subscription id), parameter details, error conditions (anonymous accounts), and functional behavior (auto-disable, signing). Fully complete.

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?

Schema coverage is 100%, but description adds significant value: concrete examples for each type (e.g., items:['5.02'] = officer change), webhook HMAC signing details, and constraints like phone verification. This far exceeds what the schema alone provides.

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 uses a specific verb (Create) and resource (subscription), states the return value (subscription id), and distinguishes from sibling tools like list_subscriptions and unsubscribe by focusing on creation. It is not a tautology.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly requires a Pipeworx OAuth account, lists supported types with example parameters, and explains delivery channels (feed always on, optional email/SMS/webhook). While it doesn't say 'when not to use', the context with sibling tools makes the usage boundaries clear.

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

All Clinicaltables 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
Disambiguation3/5

Several tool groups (ask_pipeworx/ask_pipeworx_grounded/deep_research, conditions/disease_names, polymarket_* family) have overlapping purposes, requiring careful reading of descriptions to differentiate. While many tools are conceptually distinct, the similarity within domains could lead to agent misselection.

Naming Consistency3/5

Naming is mostly snake_case but patterns vary: verb_noun (ask_pipeworx), noun_noun (entity_profile), single verb (forget, recall), and some adjectives (recent_changes). No consistent structure across the set, though individual names are descriptive.

Tool Count2/5

With 40 tools, the server is overly large for typical coherence. The tool count exceeds the 15–25 range deemed borderline, making it hard for agents to navigate and select efficiently.

Completeness4/5

The surface covers medical coding (ICD, LOINC, UCUM, drugs, procedures), financial data, prediction markets, memory, subscriptions, and meta-tools. Missing but minor elements (e.g., CPT codes) do not significantly hinder common workflows.

Resources