Skip to main content
Glama

Podcastindex

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

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

Discloses behavior beyond annotations: composite call to two services, potential 5-30s delay on bundlephobia first measurement, graceful degradation with sources_failed list. No contradiction with annotations (readOnlyHint, idempotentHint all consistent).

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?

Dense but efficient; front-loaded with core purpose. Could be slightly more concise but every sentence adds value, including performance note and fallback behavior.

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 thoroughly details return structure (summary block, per-advisory detail, links, alternative versions) and partial failure handling. Fully covers what an agent needs to know given tool complexity.

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?

Schema coverage is 100%, baseline 3. Description adds context: scoped packages accepted, version defaults to latest, and ecosystem constraint. This adds marginal but meaningful value beyond the schema's descriptions.

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 performs a composite check for adding npm packages, covering license, advisories, bundle size, etc. It distinguishes itself by specifying the exact use case ('is X safe / popular / small') and the services used (deps.dev, bundlephobia), and is unique among sibling tools.

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 states when to use ('whenever an agent asks...') and when not to ('NPM ecosystem only in v1; PyPI/Maven/Cargo/Go fall under deps.dev:version directly'), providing clear alternatives and handling of partial failures.

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

All Podcastindex 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
Disambiguation4/5

Most tools have distinct purposes, but ask_pipeworx and ask_pipeworx_grounded overlap (one is grounded), and bet_research/validate_claim/compare_entities/entity_profile all query Pipeworx data with different intents, which could cause confusion.

Naming Consistency4/5

Names are consistently lower_snake_case and mostly follow a verb_noun pattern (e.g., search_podcasts, get_podcast, list_subscriptions). A few compound names like pipeworx_feedback and polymarket_arbitrage deviate slightly but remain readable.

Tool Count2/5

30 tools is excessive for a server named 'Podcastindex'. It aggregates unrelated domains (podcasts, Pipeworx queries, Polymarket, memory, etc.), making it feel like a kitchen sink rather than a focused tool set.

Completeness3/5

For podcasts, the tool set covers search, metadata, episodes, and trending but lacks subscription management. For the broader Pipeworx domain, ask_pipeworx and discover_tools provide wide access, but specific gaps exist (e.g., no direct SEC filing query). Overall, the surface is broad but uneven.

Resources