Skip to main content
Glama

Gov Auctions

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?

Disclosures beyond annotations: composite call fanning out to two services, partial failures degrade gracefully, bundlephobia first measurement can take 5-30s, and sources_failed will list timed-out sources. All consistent with readOnlyHint, openWorldHint, idempotentHint, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is fairly long but packed with essential details. Front-loaded with main purpose. Slightly verbose but appropriate for a complex tool; concise enough for understanding.

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?

No output schema, but description enumerates all returned fields (summary block, per-advisory detail, links, alternative versions). Covers latency, partial failures, ecosystem scope. Highly complete for a composite tool.

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 has 100% coverage with descriptions for both parameters. The description adds context: scoped packages accepted, version defaults to latest. This adds minor value beyond the schema, justifying a 4.

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's a composite check for adding an npm package, covering license, advisories, version history, and bundle size. It specifies the return summary and distinguishes from siblings by noting NPM ecosystem only and referencing alternatives for other ecosystems.

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?

Explicitly states when to use: when an agent asks about safety, popularity, or size, or cost of adding a package. Also notes NPM-only scope and that other ecosystems use deps.dev directly, providing clear usage boundaries.

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

All Gov Auctions 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.9/5.0
Disambiguation2/5

Several tools occupy nearly the same question-answering niche: ask_pipeworx, ask_pipeworx_beta (currently identical by its own description), ask_pipeworx_grounded, deep_research, and validate_claim are easy to confuse. The polymarket suite also has overlapping edge/arbitrage/fill-risk boundaries, and discover_tools/suggest_questions both serve onboarding. The verbose descriptions help, but the set as a whole creates real misselection risk.

Naming Consistency4/5

Most tools follow clear snake_case verb_noun or domain-prefix patterns (auctions_search, polymarket_edges, subscribe/unsubscribe, remember/recall/forget). Minor inconsistencies exist: auction_lot_details is singular while the auction group is plural, and polymarket_edges versus polymarket_edge_tracker breaks the prefix pattern slightly. Overall the naming is predictable and readable.

Tool Count2/5

36 tools is well above the 25-tool threshold and feels bloated for a server named 'Gov Auctions': only 5 tools actually concern auctions, while the rest are general Pipeworx research, prediction-market, memory, subscription, and utility tools. Even as a general data platform, the count is heavy and includes several overlapping meta-tools.

Completeness4/5

For the auction-specific surface, the set covers search, lot details, closing-soon, historical sold prices, and data coverage, which is a solid read-only lifecycle. The main gaps are non-critical: no auction-category browser, no auction-specific alert/subscription type, and no bidding workflow. The broad research/esolution tools fill in most adjacent data needs even if they dilute the server's stated focus.

Resources