Skip to main content
Glama

Maryland MVA

by io.github.pipeworx-io

Scan Dependency

scan_dependency
Read-onlyIdempotent

Composite "should I add this npm package to my project" check in ONE call — fans out across deps.dev (license + advisories + version history) and bundlephobia (gzipped/minified bundle size, dependency count, ESM/tree-shake support). Use whenever an agent asks "is X safe / popular / small" or "what does adding lodash cost me". Returns a summary block (is_latest, license, published_at, advisory_count, bundle_kb_min, bundle_kb_gz, dependency_count, has_esm, tree_shakeable), per-advisory detail, links, and a list of recent alternative versions. NPM ecosystem only in v1; PyPI / Maven / Cargo / Go fall under deps.dev:version directly. Partial failures degrade gracefully — bundlephobia's first measurement on a new version can take 5-30s; sources_failed will list it if it times out, the rest still returns.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packageYesnpm package name. Scoped packages (e.g. "@types/node") are accepted.
versionNoSpecific version to check (e.g., "18.3.1"). Defaults to the latest published version when omitted.

Schema Changelog

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

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

The description adds behavioral context beyond annotations: it fans out to external services, partial failures degrade gracefully, and bundlephobia's first measurement can take 5-30s. Annotations already indicate read-only, idempotent, and non-destructive behavior, which the description does not contradict.

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 informative but somewhat lengthy. However, every sentence adds useful detail about the composite nature, services, use cases, ecosystem scope, and edge cases. It is well-structured with front-loaded 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 complexity of the tool (two external sources, multiple output fields) and the absence of an output schema, the description thoroughly explains what is returned (summary block, advisories, links, alternative versions) and handles edge cases like delays and failures.

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?

The input schema already provides clear descriptions for both parameters, achieving 100% coverage. The description confirms that scoped packages are accepted and that version defaults to latest, adding minor value but not essential.

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's purpose: a composite check for evaluating npm packages using deps.dev and bundlephobia. It uses specific verbs ('scan', 'fans out') and lists the exact data provided, distinguishing it from sibling tools that address different domains.

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 says when to use the tool: when an agent asks if a package is 'safe / popular / small' or what it costs. It also specifies that it's npm-only in v1, pointing to alternative tools for other ecosystems, and describes graceful degradation for partial failures.

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

All Maryland MVA 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.8/5.0
Disambiguation3/5

Most tools are distinct, but there are several problematic clusters: ask_pipeworx, ask_pipeworx_beta (which admits it is currently identical to the stable router), and ask_pipeworx_grounded can easily be misselected. The Polymarket tools (bet_research, polymarket_edges, polymarket_arbitrage, polymarket_fill_risk) also have fuzzy boundaries around 'find me an edge', and compare_entities/entity_profile/recent_changes all offer one-call company research.

Naming Consistency4/5

Naming is overwhelmingly lowercase snake_case with a verb-first pattern (ask_, generate_, list_, resolve_, subscribe, recall). Deviations include the md_dmv_ prefix on two tools, the noun-led entity_profile, and bare verbs like forget/remember/recall, but the overall style remains readable and predictable.

Tool Count2/5

33 tools is well into the bloated range for a single server, and the sprawl is worsened by the fact that only 2 of the 33 tools actually relate to the server's stated name, 'Maryland MVA.' The rest form an unrelated Pipeworx data/prediction-market/memory/meta-toolkit that could either be split into separate servers or consolidated behind the universal router.

Completeness3/5

For the actual Pipeworx domain, coverage is broad: universal routing, grounded answering, deep research, entity profiles, comparisons, claim validation, memory, and subscriptions are all present. However, for the server's apparent purpose — Maryland MVA — coverage is nearly empty: only vehicle registration counts and EV adoption exist, with no driver services, fees, offices, titles, or licensing operations. The direct tool surface also has holes (stock prices, weather, etc.) that only the meta-router papers over.

Resources