Skip to main content
Glama

Connecticut DMV

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

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

Annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=true) are not contradicted. Description adds valuable context: OAuth requirement, delivery limitations, webhook signing secret returned once, auto-disable after 10 failures. This is beyond what annotations 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?

Description is fairly long but well-structured: front-loaded with purpose and then details. Every sentence adds value, though some detail (e.g., exact webhook signature formula) could be in a separate doc. Still effective and not overly verbose given 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?

Given the tool's complexity (multiple subscription types, delivery channels, authentication requirements), the description covers usage, constraints, and return value. No output schema exists, but the description notes 'Returns the new subscription id'. Complete for an agent to use correctly.

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 meaning: explains each subscription type's parameters with examples (e.g., sec_8k with items codes, polymarket_edge with topic and min_spread_bps), delivery channel specifics (e.g., webhook JSON body HMAC signing). This goes well beyond schema 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?

The description clearly states the tool creates a proactive monitoring subscription, returns the new subscription ID, and lists supported types and delivery channels. It differentiates from siblings like unsubscribe and list_subscriptions.

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?

Provides explicit context: requires a Pipeworx OAuth account (anonymous/BYO cannot persist), supported subscription types with detailed parameters, delivery channel options and constraints (e.g., SMS must be verified, 10/day cap). No alternatives explicitly named but context is comprehensive.

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

All Connecticut DMV 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

Several tools are near-identical in purpose: ask_pipeworx and ask_pipeworx_beta are explicitly the same right now, while ai_visibility_check and scan_competitor_ai_presence overlap heavily. The only DMV-specific tool is otherwise buried among generic research, prediction-market, memory, and subscription tools that an agent would struggle to separate.

Naming Consistency3/5

Most tools use snake_case, but conventions are mixed: some are verb_noun (list_subscriptions, generate_llms_txt), some are bare verbs (remember, forget), some are brand-prefixed nouns (pipeworx_trending, polymarket_edges), and ask_pipeworx lacks a conventional verb pattern. Still readable, but not a cohesive naming scheme.

Tool Count1/5

32 tools is already heavy, but nearly all of them are unrelated to the stated Connecticut DMV scope. The server would be better served by a handful of DMV-focused tools; the current count is an extreme mismatch between name and content.

Completeness1/5

The only DMV tool is ct_dmv_ev_registrations, covering EV registration counts from a single February 2025 snapshot. There is no general vehicle registration lookup, driver licensing, plate/ VIN search, appointment, or form coverage, so the DMV domain is severely incomplete.

Resources