Skip to main content
Glama

Comicvine

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 indicate read-only, idempotent, non-destructive. Description adds behavioral details: fans out to deps.dev and bundlephobia, partial failure handling, and a note about bundlephobia's first measurement taking 5-30s. No contradiction.

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?

Description is information-dense but efficiently structured: purpose first, then usage, then output details, then limitations and failure modes. 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?

No output schema, but description thoroughly lists return fields and behavior on partial failure. Covers all essential behavioral aspects for a composite API call.

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?

Both parameters have full descriptions in schema (100% coverage). Description repeats scope acceptance but doesn't add significant new parameter-specific information beyond schema. Context on version default is implicit.

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 states 'Composite should I add this npm package to my project check in ONE call' and specifies the verb 'scan_dependency' and resource 'npm package'. It distinguishes it from 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 'Use whenever an agent asks "is X safe / popular / small" or "what does adding lodash cost me". Also notes NPM ecosystem only; alternatives for other ecosystems are given.

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

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

B3.3/5.0
Disambiguation2/5

Many tools have overlapping purposes, especially the Pipeworx utilities (ask_pipeworx, ask_pipeworx_grounded, deep_research, etc.). The comic tools are distinct but the large number of similar generally-purpose tools creates confusion across the set.

Naming Consistency3/5

Comic tools follow a consistent noun pattern (character, characters, issue, issues) but Pipeworx tools mix verb_phrase (ask_pipeworx), noun_phrase (entity_profile), and composite names (scan_competitor_ai_presence). No single convention dominates.

Tool Count1/5

The server name 'Comicvine' suggests a focused comic book reference, yet 30 of 40 tools are unrelated Pipeworx services (company financials, prediction markets, subscriptions, etc.). This is a severe scope mismatch.

Completeness2/5

The comic-related tools cover characters, issues, volumes, publishers, and creators reasonably well, but the server's overall purpose is diluted by including many non-comic tools that don't form a coherent surface. The comic subset is complete, but the full set is not.

Resources