Skip to main content
Glama

Maryland MVA

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

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

Exceeds annotations: details OAuth requirement, type-specific parameter formats, delivery channel behaviors (feed always on, email/SMS optional, webhook with signing secret and auto-disable after 10 failures). Annotations only indicate idempotent, non-destructive, open world.

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?

Dense but well-organized: purpose first, then type list with examples, then delivery channels. Every sentence adds value; no fluff. Slightly long but justified by complexity.

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?

Complete for a creation tool: covers return value (subscription id), types, parameters, delivery channels, auth requirements, and limits (10 SMS/day). No output schema, but description sufficiently documents what is returned.

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 extensive examples for each type (e.g., sec_8k items, polymarket_edge topic), constraint details (phone verification, webhook restrictions), and clarifies delivery schema beyond what JSON schema 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?

Clear verb 'Create' and resource 'proactive monitoring subscription' immediately in first sentence. Returns subscription id. Distinguishes from siblings 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?

States when to use (creating new subscription) and lists prerequisites (OAuth account for persistence, phone verification for SMS). No explicit exclusion for duplicate subscriptions, but idempotent annotation suggests safe re-call.

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

All Maryland MVA 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.8/5.0
Disambiguation3/5

Most tools are distinct, but there are several problematic clusters: ask_pipeworx, ask_pipeworx_beta (which admits it is currently identical to the stable router), and ask_pipeworx_grounded can easily be misselected. The Polymarket tools (bet_research, polymarket_edges, polymarket_arbitrage, polymarket_fill_risk) also have fuzzy boundaries around 'find me an edge', and compare_entities/entity_profile/recent_changes all offer one-call company research.

Naming Consistency4/5

Naming is overwhelmingly lowercase snake_case with a verb-first pattern (ask_, generate_, list_, resolve_, subscribe, recall). Deviations include the md_dmv_ prefix on two tools, the noun-led entity_profile, and bare verbs like forget/remember/recall, but the overall style remains readable and predictable.

Tool Count2/5

33 tools is well into the bloated range for a single server, and the sprawl is worsened by the fact that only 2 of the 33 tools actually relate to the server's stated name, 'Maryland MVA.' The rest form an unrelated Pipeworx data/prediction-market/memory/meta-toolkit that could either be split into separate servers or consolidated behind the universal router.

Completeness3/5

For the actual Pipeworx domain, coverage is broad: universal routing, grounded answering, deep research, entity profiles, comparisons, claim validation, memory, and subscriptions are all present. However, for the server's apparent purpose — Maryland MVA — coverage is nearly empty: only vehicle registration counts and EV adoption exist, with no driver services, fees, offices, titles, or licensing operations. The direct tool surface also has holes (stock prices, weather, etc.) that only the meta-router papers over.

Resources