Skip to main content
Glama

nouel

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.

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark readOnly/openWorld/idempotent, and the description adds behavioral context: it fans out across two services, degrades gracefully on partial failures, and notes bundlephobia's first measurement can take 5-30s. It also discloses the sources_failed field. 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.

Conciseness5/5

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

Five dense sentences, each earning its place: purpose, usage, return payload, ecosystem scope, and failure mode. It's front-loaded with the core implication and structured for skimming.

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?

For a composite tool with no output schema, the description lists the summary block fields, per-advisory detail, links, alternative versions, and failure behavior. It covers edge cases (timeout, non-NPM packages) and gives a complete picture of what the agent will receive.

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?

The input schema covers both parameters with 100% coverage, including package name format and version default behavior. The description does not add new parameter-level meaning beyond restating the schema, so the baseline of 3 applies.

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 a specific verb and resource: a composite 'should I add this npm package to my project' check. It names the data sources (deps.dev and bundlephobia) and specific checks (license, advisories, bundle size, etc.), distinguishing it from any sibling tool (none cover npm package adoption).

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?

It gives explicit trigger phrases ('is X safe / popular / small', 'what does adding lodash cost me') and explicitly scopes to NPM in v1, directing non-NPM ecosystems to deps.dev:version directly. This provides both when-to-use and when-not-to-use guidance.

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

All nouel 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

Several tool groups have overlapping purposes (e.g., ask_pipeworx, ask_pipeworx_grounded, deep_research all query Pipeworx data; polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker all analyze prediction markets). Descriptions help distinguish them, but the boundaries are not always clear.

Naming Consistency3/5

Tool names are mostly descriptive but mix conventions: some are verb_noun (list_subscriptions, get_prizes_by_year), others are noun_verb (pipeworx_feedback, polymarket_edges), and a few are single verbs (remember, recall). No strong pattern, but still readable.

Tool Count4/5

With 32 tools, the server covers a wide range of domains (data querying, prediction markets, company analysis, Nobel prizes, memory, subscriptions). The count is high but each tool serves a specific purpose, justifying the breadth.

Completeness4/5

The tool set provides comprehensive coverage for its stated domains: data retrieval, entity resolution, comparison, monitoring, and memory. Minor gaps exist (e.g., no direct bet placement on Polymarket), but core workflows are well-supported.

Resources