Skip to main content
Glama

North Carolina 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.4/5.0
Behavior4/5

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

Annotations present (idempotentHint=true). Description adds useful behavioral details: OAuth requirement, phone verification need, webhook auto-disable after 10 failures, and HMAC signing. Could be more explicit about idempotency behavior (e.g., duplicate subscription handling) but still adds value.

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?

Somewhat long but well-organized: main purpose first, then type-specific params, then delivery channels. Every sentence adds value. Minor verbosity in delivery section could be tightened, but overall effective.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers all key aspects: auth, supported types with param details, delivery channels with prerequisites and constraints. No output schema, but description mentions return of subscription id. Could add success/error handling or rate limits beyond SMS cap, but largely complete for a creation tool.

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?

100% schema coverage baseline is 3. Description greatly enriches parameter meaning with concrete examples (e.g., 'items:["5.02"] = officer change', 'min_spread_bps?:500') and detailed delivery channel constraints (phone verification, SMS cap, webhook HMAC). Exceeds schema detail.

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 verb 'Create' and the resource 'proactive monitoring subscription', with immediate output detail ('Returns the new subscription id'). It distinguishes itself from siblings like list_subscriptions, unsubscribe, and recent_alerts by focusing on creation and live-data event streams.

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?

Explicit guidance on prerequisite (Pipeworx OAuth account), unsupported auth types (anonymous/BYO), and delivery channel options with constraints (phone verification, 10/day SMS cap). Lacks explicit 'when not to use' but covers context well.

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

All North Carolina 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

The set contains several families with blurred boundaries: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all answer questions over the same routed data, and polymarket_edges, polymarket_edge_tracker, polymarket_arbitrage, and polymarket_fill_risk overlap heavily. The two NC DMV tools are clear, but an agent could easily pick the wrong member of these near-duplicate families despite detailed descriptions.

Naming Consistency3/5

Most names are readable snake_case and several families share prefixes (nc_dmv_, ask_pipeworx, polymarket_), but the set mixes verb phrases (compare_entities, search_within), noun phrases (entity_profile, recent_alerts), and bare verbs (remember, forget). The convention is not unified, though individual clusters are internally consistent.

Tool Count2/5

33 tools is already heavy, but the bigger problem is that only two tools (nc_dmv_offices, nc_dmv_wait_times) belong to the stated North Carolina DMV domain; the other 31 are an unrelated general-purpose data and research toolkit. The count is not scoped to the server's apparent purpose.

Completeness1/5

For a North Carolina DMV surface, the tool set is severely incomplete: it offers office lookup and live wait times but nothing for appointments, license renewal, vehicle registration, fees, forms, or eligibility. Agents attempting real DMV tasks would hit dead ends immediately.

Resources