Skip to main content
Glama

Open Notify

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 mark as read-only/idempotent. Description adds critical context: composite fan-out, partial failures, up-to-30s timeout on bundlephobia first measurement, and graceful degradation.

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?

Well-structured and front-loaded. Slightly verbose with run-on sentences, but every sentence adds value.

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, description enumerates exact return fields, covers failure modes, and ecosystem limitations. Complete for a composite tool.

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 coverage is 100%. Description reinforces 'scoped packages accepted' and default to latest version when omitted, adding value beyond 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?

Description clearly states it's a composite check for npm packages, querying deps.dev and bundlephobia. Distinct from all sibling tools which are unrelated.

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 says when to use ('is X safe/popular/small') and limits to NPM ecosystem, directing other ecosystems to deps.dev:version directly.

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

All Open Notify 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.6/5.0
Disambiguation2/5

The three ask_pipeworx variants are near-identical (the beta is currently an exact copy of the stable router), and ask_pipeworx, ask_pipeworx_grounded, deep_research, and validate_claim all route natural-language questions to the same underlying source catalog. The six polymarket_* tools also heavily overlap in opportunity detection, though some clusters like memory and subscriptions are clearly separated.

Naming Consistency3/5

The naming is mostly snake_case but mixes conventions: verb_noun (list_subscriptions, resolve_entity), noun-first (entity_profile, bet_research), metadata-style prefixes (pipeworx_trending, polymarket_edges), and bare verbs (remember, recall, forget). It is readable but does not follow one predictable pattern across the set.

Tool Count2/5

33 tools is excessive for a server nominally named Open Notify, and the count is inflated by redundant ask_pipeworx variants and six closely-related Polymarket tools. The broad data-gateway scope could justify a large catalog, but the set feels bloated and unfocused rather than deliberately scaled.

Completeness2/5

For the apparent Open Notify domain, only astros and iss_now fit, and core ISS functionality like pass predictions is missing. The wider data-lookup surface is extensive, but the inclusion of unrelated memory, subscription, npm-scanning, and llms.txt tools means no single domain gets coherent lifecycle coverage.

Resources