Skip to main content
Glama

Or Dmv Wait Times

or_dmv_wait_times
Read-onlyIdempotent

Live wait times at Oregon DMV field offices, published by ODOT DMV itself: the current average minutes until served and how many customers are queued at each of the 60 offices statewide. Answers "how long is the wait at the Portland DMV", "which Oregon DMV office is fastest right now", "is the Salem DMV busy", or "shortest DMV line near Eugene". Oregon is one of only two states whose DMV publishes a live queue feed. Offices report only during business hours; outside them each comes back as not_reporting with a null wait, which is the agency switching the feed off rather than an office with no line.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoCity name, matched as a substring, e.g. "Eugene", "Medford".
sortNo"wait" ranks shortest reported wait first (reporting offices first); "name" (default) keeps the agency's own order.
limitNoMax offices to return (default 60, max 100).
officeNoCase-insensitive office-name substring, e.g. "Portland", "Beaverton", "Bend".
regionNoODOT region substring. One of Central Oregon, Eastern Oregon, Portland Area, Southern Oregon, The Coast, Willamette Valley.
open_onlyNoWhen true, keep only offices currently reporting a live wait.

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?

The description adds significant behavioral context beyond annotations, such as data source (ODOT DMV), live nature of data, and reporting hours with null wait handling. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, front-loaded with the core purpose, followed by examples and edge-case behavior. Every sentence adds value without redundancy.

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?

The description covers all essential aspects: data type, availability, filtering options, and limitations. While no output schema is provided, the description adequately conveys what to expect.

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?

Schema coverage is 100%, and the description adds value by explaining what the returned data represents (average wait, queue size), enriching understanding of parameters like 'sort' and 'open_only'.

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 specifies the tool's purpose: providing live wait times at Oregon DMV field offices, with specific examples of queries it answers. It distinguishes itself from the sibling tool 'or_dmv_offices' by focusing on live queue data.

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 clear context for usage, including example queries and the behavior outside business hours. It does not explicitly list when not to use, but the context is sufficient for typical use cases.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.