Skip to main content
Glama

Delaware DMV

by io.github.pipeworx-io
OverviewAdmin

De Dmv Ev Adoption

de_dmv_ev_adoption
Read-onlyIdempotent

Measure electric-vehicle adoption in Delaware from DMV registration counts: how many battery-electric and plug-in hybrid vehicles are registered statewide and what share of every registered Delaware vehicle they represent. Returns the plug-in total, the battery-electric and plug-in hybrid counts separately, and the plug-in share of the whole fleet. Answers "what percentage of cars in Delaware are electric", "how many EVs are registered in Delaware", and "how many plug-in hybrids are in Delaware". Delaware publishes this statewide, refreshed monthly. For the rebates Delaware paid on EV purchases use de_dmv_ev_rebates; for home and workplace charger rebates use de_dmv_charger_rebates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive. The description adds value by stating the data is 'refreshed monthly', providing freshness context beyond 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?

Four front-loaded sentences that efficiently convey purpose, examples, and sibling differentiation with zero waste.

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?

For a parameterless tool, the description covers purpose, output details (counts, share), example questions, data source, refresh frequency, and sibling links. Fully complete.

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?

Input schema has zero parameters, so no parameter documentation is needed. With 0 params, baseline is 4, and the description does not need to add param info.

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 ('measure'), resource ('EV adoption in Delaware'), and scope ('statewide DMV registration counts'). It also distinguishes from sibling tools by naming them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use this tool ('monthly refreshed') and when not to, providing exact sibling tool names for rebates and charger rebates.

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

All Delaware 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.

Resources