Skip to main content
Glama

Delaware DMV

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

Schema Changelog

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

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Adds behavioral context beyond annotations: describes retention duration (persistent for authenticated users, 24 hours for anonymous) and scoping by identifier. No contradiction with annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false).

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?

Single paragraph, front-loaded with main purpose, followed by usage guidelines and behavioral details. Every sentence adds value; no 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?

For a simple 2-parameter tool with no output schema, the description covers purpose, usage, persistence, and related tools. Could add error handling or size limits, but is largely 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?

Schema coverage is 100%, baseline 3. Description adds example values for key and clarifies value as 'any text', enhancing the bare schema descriptions.

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 uses a specific verb ('Save') and resource ('data the agent will need to reuse later') and explicitly distinguishes from siblings by naming recall and forget. The purpose is unambiguous.

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?

Provides explicit when-to-use examples (resolved ticker, target address, user preference) and mentions related tools (recall, forget) for retrieval and deletion. Does not explicitly state when not to use, but the guidance is clear.

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.

TDQS

A3.6/5.0
Disambiguation2/5

Several tools are effectively duplicates or near-duplicates: ask_pipeworx and ask_pipeworx_beta are described as currently identical, ai_visibility_check and scan_competitor_ai_presence overlap heavily, and the polymarket_arbitrage/polymarket_edges/polymarket_fill_risk cluster has fuzzy boundaries. Even within the DMV subset, de_dmv_ev_adoption and de_dmv_vehicle_registrations both answer overlapping EV-count questions.

Naming Consistency2/5

The de_dmv_* tools follow one snake_case pattern, but the rest of the set mixes bare nouns, brand-prefixed verbs, and generic names (entity_profile, remember, generate_llms_txt, ask_pipeworx_beta). There is no consistent verb_noun or domain-prefix convention across the 36 tools.

Tool Count2/5

36 tools is over the threshold where a tool set becomes hard to navigate, and most of them have nothing to do with a Delaware DMV server. Only five tools are DMV-related; the rest are a general-purpose Pipeworx data, memory, and prediction-market toolkit, which makes the set feel bloated and mis-scoped.

Completeness2/5

For a server named Delaware DMV, the surface is missing core DMV capabilities like driver licenses, vehicle titling, registration renewals, appointments, or fee lookups. The five de_dmv_* tools cover only EV adoption, rebates, charger rebates, crash stats, and registration counts, leaving obvious domain gaps.

Resources