Skip to main content
Glama

Data Pa

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.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint true, and destructiveHint false. The description adds value by mentioning partial failures degrading gracefully, the timing caveat for bundlephobia's first measurement (5-30s), and the sources_failed field. This provides useful behavioral 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.

Conciseness4/5

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

The description is informative and front-loaded with the composite purpose. However, it is somewhat dense with technical details, which slightly reduces conciseness. Still, every sentence adds value, and it is well-structured.

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?

Despite no output schema, the description thoroughly details the return values (summary block, per-advisory detail, links, alternative versions) and partial failure behavior. This is complete for a tool of this complexity.

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 coverage is 100% with descriptions for both parameters. The description adds context about scoped packages being accepted and version defaulting to latest, but this aligns with schema descriptions. With high schema coverage, the baseline is 3, and the description adds minimal extra meaning.

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 adding an npm package, including license, advisories, version history, and bundle size. It differentiates from siblings by focusing on npm and the specific use case of evaluating an npm package's safety, popularity, or size.

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 provides usage context: 'Use whenever an agent asks "is X safe / popular / small" or "what does adding lodash cost me".' It also specifies ecosystem limitation (NPM only in v1) and mentions alternatives for other ecosystems, providing clear guidance on when to use this tool.

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

All Data Pa 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 clusters blur together: ask_pipeworx, ask_pipeworx_beta (explicitly identical today), and ask_pipeworx_grounded share routing, while discover_tools/suggest_questions and the Polymarket edge/arbitrage/fill-risk tools have overlapping discovery purposes. Rich descriptions reduce some confusion, but an agent must read carefully to avoid misselection.

Naming Consistency3/5

Most names are lowercase snake_case, but there is no consistent verb_noun pattern: ask_pipeworx/beta/grounded and polymarket_* are domain-prefixed, entity_profile/recent_changes are noun phrases, and query/metadata/remember are bare verbs or nouns. The naming is still readable and subfamilies share prefixes, so it is mixed rather than chaotic.

Tool Count2/5

34 tools is above the comfortable range for a single MCP server, and several could be folded together (the beta variant, visibility checks, and Polymarket scanners). The breadth reflects a large platform, but the surface feels heavy for an agent to select from confidently.

Completeness4/5

The query side is strong: PA Open Data has datasets/metadata/query coverage, and Pipeworx provides ask, deep_research, entity_profile, compare, recent_changes, validate_claim, plus subscriptions and memory with lifecycle coverage. Minor gaps: descriptions promise resolvable pipeworx:// citations but no resource/read tool is exposed, and there is no direct way to fetch an arbitrary record by citation.

Resources