Skip to main content
Glama

Espn

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.9/5.0
Behavior5/5

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

The description adds significant behavioral context beyond annotations: it fans out across two external services, handles partial failures gracefully, and notes a potential 5-30s delay for bundlephobia's first measurement. Annotations already indicate read-only, idempotent, non-destructive behavior, and the description is consistent.

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?

The description is a single, well-organized paragraph that front-loads the core purpose. Every sentence adds meaningful information without redundancy. It efficiently covers purpose, usage, behavioral notes, and return structure.

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 explains the return value structure, including specific fields and their meanings. It also covers ecosystem limitations and best-effort behavior, making the tool's behavior fully transparent for an agent.

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?

Both parameters are fully described in the schema (100% coverage). The description adds valuable context: scoped packages are accepted, and version defaults to latest. This extra clarification aids correct usage beyond the schema alone.

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 as a composite check for npm packages, specifying the resources (deps.dev and bundlephobia) and the question it answers ('should I add this npm package'). It effectively distinguishes itself from sibling tools through its specific domain and composite nature.

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 tells when to use this tool (agent asks about npm package safety, size, popularity) and when not to (PyPI, Maven, etc., which should use deps.dev directly). It also notes partial failure behavior and timeout considerations, providing clear guidance for selection and invocation.

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

All Espn 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
Disambiguation3/5

Several tools cluster around similar purposes—the three ask_pipeworx variants, the five polymarket_* analysis tools, and the meta/discovery tools (discover_tools, suggest_questions, pipeworx_trending)—so an agent could plausibly call the wrong one. However, the descriptions are exceptionally detailed with explicit 'use this when' guidance, which mitigates most confusion.

Naming Consistency3/5

Names are almost all snake_case, but there is no consistent verb_noun or resource_action pattern: ask_pipeworx, entity_profile, remember, get_scoreboard, polymarket_fill_risk, etc. Pairs like remember/recall/forget and subscribe/unsubscribe are consistent, but the broader set mixes verbs, nouns, and prefixes (ask_, pipeworx_, polymarket_, get_, scan_) without a unified scheme.

Tool Count2/5

36 tools is well over the 25-tool 'heavy' threshold, and the set spans multiple unrelated domains: sports data, a general structured-data router, prediction-market analysis, memory storage, and user feedback. Many tools are meta or auxiliary (suggest_questions, pipeworx_feedback, remember/recall/forget) that don't clearly belong to the server's core purpose, making the set feel bloated.

Completeness3/5

For a sports-data server, core score/news/standings/team/schedule operations exist, but player stats, game details, injuries, and playoff brackets are missing. For the broader Pipeworx data platform the surface is extensive, but the mix of domains makes it hard to declare the set complete for any single stated purpose.

Resources