Skip to main content
Glama

Vessel Tracking

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

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

Beyond the annotations, the description reveals critical side effects and constraints: subscription persistence requiring OAuth, SMS phone verification and daily cap, webhook auto-disable after consecutive failures, and one-time delivery of the webhook signing secret. This is rich behavioral context that annotations alone do not provide.

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 longer than average but every sentence carries specific operational detail. It is front-loaded with the core purpose and then organizes supporting details by subscription type and delivery channel. Some content (e.g., delivery constraints) is duplicated from the schema, preventing a perfect score.

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?

Despite having no output schema, the description is fully complete for a complex tool: it covers all five subscription types, required auth, all delivery channels with their caveats, rate limits, and how to consume the feed. Nothing critical appears missing.

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?

The schema already covers parameter details with 100% coverage, so the baseline is 3. The description adds concrete semantic meaning beyond the schema, such as items:['5.02'] meaning officer change and topic:'fed' for Polymarket mispricings, making it slightly more helpful.

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 ('Create a proactive monitoring subscription to a live-data event stream') and enumerates the exact supported subscription types. This clearly distinguishes 'subscribe' from sibling tools like list_subscriptions, unsubscribe, and 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?

The description provides strong contextual usage guidance: it names requirements (Pipeworx OAuth account), explains type-specific configs, and even mentions alternative pull methods (recent_alerts or GET registry.pipeworx.io/alerts.json). It lacks an explicit 'when not to use' statement, so it stops short of a 5.

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

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

Several tools have significantly overlapping purposes, especially the ask_pipeworx family, deep_research, and validate_claim, plus a dense cluster of polymarket_* tools and two AI-visibility checkers. The ship-related tools are distinct, but an agent would struggle to choose among the many broadly similar query/research tools.

Naming Consistency3/5

Names are mostly snake_case and readable, but they follow no consistent convention: generic one-word verbs like remember and forget sit alongside branded names like ask_pipeworx, noun-style names like entity_profile, and prefix families like polymarket_*. The inconsistency is noticeable but not chaotic.

Tool Count2/5

34 tools is well above the well-scoped range, and the vast majority are unrelated to the server name 'Vessel Tracking'. The live-ship tools are a tiny minority buried inside a broad general-purpose data, research, and prediction-market platform, making the overall set feel bloated and misaligned with its stated identity.

Completeness1/5

As a vessel-tracking server, the surface is severely incomplete: only ais_coverage_check, live_ship_position, and live_ships_in_area relate to shipping, with no vessel lookup by name/IMO, no historical positions, no voyage data, and no port-call information. The actual tool set is rich as a general data platform, but that is not what the server name promises.

Resources