Skip to main content
Glama

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

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

The description adds significant behavioral details beyond annotations: OAuth requirement, type-specific parameters, delivery constraints (phone verification, SMS cap), and webhook signing details. No contradiction with annotations.

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 detailed but well-structured, starting with the core purpose and then expanding on types and delivery. While lengthy, every sentence provides necessary context for a complex tool.

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 and absence of an output schema, the description fully covers all aspects: supported types, parameter structures, delivery options, and prerequisites. It is complete for accurate invocation.

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?

With 100% schema coverage, the description adds substantial meaning by explaining each parameter's purpose, providing examples per type, and detailing delivery object properties. It goes far beyond the basic schema.

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 that the tool creates a proactive monitoring subscription to a live-data event stream and returns the subscription ID. It distinguishes the tool from siblings like list_subscriptions and unsubscribe by focusing on subscription creation.

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 specifies when to use (proactive monitoring, subscription) and prerequisites (Pipeworx OAuth account). It also details supported types and delivery channels. However, it lacks explicit guidance on when not to use or alternatives for pulling alerts.

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

All Oregon 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.6/5.0
Disambiguation2/5

Several tools occupy the same functional space: ask_pipeworx and ask_pipeworx_beta are explicitly identical right now, and the Polymarket cluster (polymarket_edges, polymarket_arbitrage, polymarket_edge_tracker, polymarket_fill_risk, bet_research) heavily overlaps in purpose. The only clearly separated tools are the two DMV-specific ones, but they are drowned out by ambiguous data-query and prediction-market tools.

Naming Consistency4/5

Tool names mostly follow a predictable snake_case verb_noun pattern such as list_subscriptions, resolve_entity, validate_claim, and the polymarket_* / or_dmv_* prefixes are consistent. Minor deviations like bet_research, pipeworx_feedback, and ask_pipeworx_beta break the pattern slightly, but the overall style is coherent and readable.

Tool Count1/5

A server named 'Oregon DMV' exposes 33 tools, only 2 of which relate to DMV office locations and wait times. The other 31 tools form a broad general-purpose data and prediction-market platform, making the count and scope an extreme mismatch for the stated server identity.

Completeness1/5

For an Oregon DMV server, the surface is severely incomplete: there are no tools for appointments, forms, fees, licensing, registration, or services. The two DMV tools cover only office addresses and live wait times, covering a tiny slice of the domain implied by the server name.

Resources