Skip to main content
Glama

Tennessee Driver Services

by io.github.pipeworx-io
OverviewAdmin

Tn Dmv Driver Service Centers

tn_dmv_driver_service_centers
Read-onlyIdempotent

Find Tennessee driver service centers (Department of Safety and Homeland Security) with street address, county, hours, phone, coordinates, and exactly which services each of the 186 locations performs. Tennessee publishes a per-location capability matrix, so this answers questions a plain address list cannot: "which Tennessee driver service center issues a REAL ID", "where can I take the CDL skills test in Tennessee", "which Tennessee location does handgun permits", "where do I get a vision test near Knoxville", or "is there a driver services kiosk in Memphis". Locations split into full service centers, self-service kiosks, county clerk partners and express counters. Filter by city, county, ZIP, name or required service; call with no arguments for all 186.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zipNoFive-digit Tennessee ZIP code, or a prefix, e.g. "37830".
cityNoCity name, e.g. "Nashville", "Oak Ridge". Matched loosely, so spacing does not matter.
nameNoLocation-name substring, e.g. "Oak Ridge", "Express".
limitNoMax locations to return (default 50, max 200).
countyNoTennessee county name, matched as a substring, e.g. "Davidson", "Shelby".
serviceNoRequire a service, matched as a substring. Published services: REAL ID, new application, photo ID, handgun permit, vision test, road or motorcycle test, knowledge test, CDL skills test, renewal, name change, address change, graduated license upgrade, duplicate license, motor vehicle report, set up a payment plan, pay reinstatement fees, submit reinstatement documentation, full service, express service, third-party testing, self-service kiosk.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations indicate readOnly, openWorld, idempotent, and non-destructive behavior. The description adds valuable context beyond annotations by explaining the data source (Tennessee's per-location capability matrix), the exact services provided, and the scope (186 locations). It is consistent with annotations and provides no contradictions.

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 a single paragraph that flows logically: core purpose, example queries, location types, and filtering options. Every sentence adds value, but it could be slightly more concise. It is well-structured and front-loaded with the main purpose.

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 6 parameters and no output schema, the description provides a complete overview. It explains the types of locations, the services matrix, and filtering capabilities. The return content (address, county, hours, phone, coordinates) is explicitly mentioned, making the tool's behavior understandable without an output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% coverage with descriptions for all 6 parameters. The tool description mentions filtering criteria (city, county, ZIP, name, service) but does not add new semantics beyond what the schema provides. Baseline of 3 is appropriate as the schema is sufficient.

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 finds Tennessee driver service centers with detailed information including street address, county, hours, phone, coordinates, and services. It lists specific example queries and distinguishes between location types (full service, kiosks, etc.). The name and title are clear, and it differentiates from sibling tool tn_dmv_impaired_driving_crashes.

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 explicit usage examples like 'which Tennessee driver service center issues a REAL ID' and states 'call with no arguments for all 186'. It implies when to use this tool over alternatives but does not explicitly list exclusions or when not to use it. The context is clear but lacks explicit directive for alternative tools.

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

All Tennessee Driver Services 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.

Resources