Skip to main content
Glama

Always Seven

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. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already indicate readOnly, openWorld, idempotent, non-destructive. The description adds critical behavioral context: partial failures degrade gracefully, bundlephobia's first measurement can take 5-30s, and sources_failed lists timeouts. No contradiction with 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 detailed and well-structured, starting with the composite check, then data sources, usage guidance, ecosystem constraints, and graceful degradation. Slightly verbose but every sentence adds value; front-loaded effectively.

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 having no output schema, the description comprehensively lists return fields (summary block, advisories, links, alternatives) and explains partial failure behavior. All necessary context for correct invocation is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% with clear descriptions. The description adds context: version defaults to latest, scoped packages accepted, and example formats like '18.3.1' and '@types/node'. This enhances 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 tool's purpose: a composite check for npm packages using deps.dev and bundlephobia. It specifies the verb (scan/check), resource (npm dependency), and distinguishes from siblings by being npm-specific.

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?

Provides explicit when-to-use guidance: 'Use whenever an agent asks "is X safe / popular / small"...' and when-not-to-use: 'NPM ecosystem only in v1; PyPI / Maven / Cargo / Go fall under deps.dev:version directly.' This effectively advises on alternatives.

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

All Always Seven 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
Disambiguation2/5

Several tools overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route natural-language questions to the same underlying 5,708-tool catalog, and ask_pipeworx_beta is explicitly identical today. The Polymarket family (bet_research, polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, polymarket_edge_tracker, polymarket_kalshi_spread) also has fuzzy boundaries — both bet_research and polymarket_edges claim 'should I bet on X', and discover_tools versus suggest_questions both serve discovery. Despite very detailed descriptions, an agent would frequently struggle to pick the correct tool.

Naming Consistency3/5

The naming is mostly snake_case and readable, with coherent micro-families (polymarket_*, pipeworx_*, ask_pipeworx variants, remember/recall/forget). However, patterns are mixed: verb_noun (compare_entities, resolve_entity, generate_llms_txt) sits alongside noun-led names (entity_profile, recent_alerts, pipeworx_trending), and entity-related tools use three different conventions (compare_entities, resolve_entity, entity_profile). It's consistent within families but not across the full set.

Tool Count2/5

32 tools is well past the 25-tool threshold for a coherent set, and the scope is a scattered grab bag: a joke RNG, an AI-visibility probe, a 5,708-tool data router, prediction-market arb analytics, key-value memory, subscriptions, npm dependency scanning, llms.txt generation, and a feedback channel. Some of these are arguably platform additions rather than core tools, but as presented the count feels bloated and unfocused.

Completeness3/5

The major workflow areas are well covered — data lookup has routing, grounded mode, deep research, entity resolution, comparisons, profiles, and change feeds; memory and subscriptions each have full lifecycle coverage. However, the server repeatedly references pipeworx:// citation URIs as fetchable yet provides no record-fetching tool, and the diffuse purpose makes it hard to assess what 'complete' even means. Notable gaps exist around citation resolution and execution of the arbitrage signals the Polymarket tools generate.

Resources