Skip to main content
Glama

North Carolina 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.2/5.0
Behavior4/5

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

The description adds useful behavioral context beyond annotations: memory scoping by identifier, persistence differences between authenticated (persistent) and anonymous (24-hour) sessions. No contradiction with annotations (idempotentHint=true implies safe re-save).

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 (three sentences) and well-structured: purpose first, then usage guidance, then behavioral notes. Every sentence adds value.

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 is complete for a store operation with no output schema. It covers purpose, when to use, memory scoping, and persistence. Could mention return confirmation but not essential.

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?

Schema description coverage is 100%, so the schema already documents the two parameters. The description provides usage examples but no additional format or constraint details 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 the verb 'save' and the resource 'data the agent will need to reuse later', with specific examples like 'resolved ticker', 'target address'. It distinguishes from sibling tools 'recall' and 'forget' by mentioning them directly.

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 explains when to use ('when you discover something worth carrying forward') and provides examples. It mentions pairing with 'recall' and 'forget' as alternatives but does not explicitly state when not to use.

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

All North Carolina 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.5/5.0
Disambiguation2/5

The set contains several families with blurred boundaries: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all answer questions over the same routed data, and polymarket_edges, polymarket_edge_tracker, polymarket_arbitrage, and polymarket_fill_risk overlap heavily. The two NC DMV tools are clear, but an agent could easily pick the wrong member of these near-duplicate families despite detailed descriptions.

Naming Consistency3/5

Most names are readable snake_case and several families share prefixes (nc_dmv_, ask_pipeworx, polymarket_), but the set mixes verb phrases (compare_entities, search_within), noun phrases (entity_profile, recent_alerts), and bare verbs (remember, forget). The convention is not unified, though individual clusters are internally consistent.

Tool Count2/5

33 tools is already heavy, but the bigger problem is that only two tools (nc_dmv_offices, nc_dmv_wait_times) belong to the stated North Carolina DMV domain; the other 31 are an unrelated general-purpose data and research toolkit. The count is not scoped to the server's apparent purpose.

Completeness1/5

For a North Carolina DMV surface, the tool set is severely incomplete: it offers office lookup and live wait times but nothing for appointments, license renewal, vehicle registration, fees, forms, or eligibility. Agents attempting real DMV tasks would hit dead ends immediately.

Resources