Skip to main content
Glama

Tennessee Driver Services

by io.github.pipeworx-io
OverviewAdmin

Tn Dmv Impaired Driving Crashes

tn_dmv_impaired_driving_crashes
Read-onlyIdempotent

Count Tennessee injury and fatal traffic crashes involving alcohol or drugs, from the Department of Safety and Homeland Security crash file for calendar year 2022. Each record is one person involved in an impaired-driving crash, carrying crash severity (fatal, suspected serious injury, suspected minor injury), the driver age group and gender, the investigating law-enforcement agency, date, time and coordinates. Answers "how many fatal DUI crashes in Tennessee", "which age group is involved in the most alcohol-related crashes in Tennessee", "drug-involved crashes by police agency", or "impaired driving crashes by month". Group results by age_group, gender, severity, agency, substance or month, and get a sample of the underlying records with latitude and longitude for mapping.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax sample records returned alongside the counts (default 10, max 200).
agencyNoInvestigating agency substring. State troopers are published as "THP District 3 - Nashville" and similar, so "THP" selects all of them; city forces read "METROPOLITAN NASHVILLE POLICE DEPT", "MEMPHIS POLICE DEPT"; counties read "SHERIFF".
genderNoPublished as "M" or "F"; "male"/"female" are accepted.
group_byNoBreakdown dimension: age_group, gender, severity, agency, substance, month. Defaults to age_group.
severityNoCrash severity substring: "fatal", "serious injury", "minor injury".
age_groupNoAge band substring as published, e.g. "21 to 24", "80 & Up", "16 to 17".
substanceNo"alcohol", "drugs", "both" (alcohol and drugs together), or "either" (default — any impairment).

Schema Changelog

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

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare readOnly, idempotent, non-destructive. Description adds specific behavior: returns counts plus sample records with coordinates, group_by capability, and limit defaults. Consistent 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 moderately long but front-loads the core purpose and packs relevant details efficiently. Every sentence contributes useful information.

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?

Given 7 parameters and no output schema, the description covers parameter usage, grouping, and sample output well. Could be enhanced by listing possible age_group values, but overall sufficient.

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% with descriptions for each parameter. The description adds value by providing concrete examples for agency, substance values, and group_by dimension options, beyond the 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 it counts Tennessee impaired driving crashes from a specific data source and year, with example queries. It is distinct from sibling tools like tn_dmv_driver_service_centers.

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 about what the tool does and gives example questions, but does not explicitly contrast with alternatives or state when not to use it.

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