Skip to main content
Glama

Fda Devices

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.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations indicate idempotency and non-destructive creation. Description adds details: account requirement, type-specific parameters, delivery constraints (SMS cap, webhook signing secret), and that subscriptions persist. No contradictions.

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?

Well-structured with key info upfront in first sentence, followed by organized details for types and delivery. While lengthy, it efficiently packs necessary complexity without redundancy.

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?

Covers all relevant aspects: purpose, required authentication, type selection with examples, delivery options with limitations, return value, and side effects. No output schema needed as description sufficiently explains behavior.

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 enriches each parameter with concrete examples, type-specific filters, and delivery channel constraints that go well beyond the schema's brief 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?

Clearly states the verb (Create), resource (subscription to event stream), and outcome (returns id). Distinguishes from sibling tools like list_subscriptions and unsubscribe by focusing on creation and monitoring.

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?

Specifies when to use (proactive monitoring), required account type, supported types, and delivery channels with constraints. Implicitly contrasts with pulling alerts via recent_alerts or API endpoint, but could explicitly compare to alternative tools.

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

All Fda Devices 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

The FDA-specific tools are distinct, but they are mixed with many generic Pipeworx tools (e.g., ask_pipeworx variants, deep_research, entity_profile) that have overlapping purposes. This creates significant ambiguity for an agent trying to choose the right tool for FDA-related queries.

Naming Consistency2/5

Tool names follow two inconsistent patterns: FDA tools use 'fda_device_*' (consistent), while generic tools use various patterns like 'ask_pipeworx', 'deep_research', 'remember', etc. The mix of snake_case, camelCase, and descriptive phrases lacks coherence.

Tool Count2/5

With 37 tools, the count is high for what is intended as an FDA devices server. Only 6 tools are directly FDA-related; the rest are generic and dilute the purpose. The scope is mismatched, making the tool count inappropriate.

Completeness3/5

The FDA tools cover key areas: 510k search, adverse events, PMA, recalls, company profiles. However, the server is incomplete for its name because it lacks many tools that a comprehensive FDA devices server would have, and the generic tools don't fill those gaps.

Resources