Skip to main content
Glama

Shodan

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

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint=true; description adds critical behavioral detail: bundlephobia first measurement can take 5-30s, partial failures degrade gracefully, and sources_failed will list timed-out sources. This goes beyond annotations without contradicting them.

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?

Description is comprehensive but somewhat lengthy. It is front-loaded with the primary purpose in the first sentence. Every sentence adds useful information, though slight tightening could improve conciseness. Still well-structured and clear.

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 fully explains return value: summary block with specified fields, per-advisory details, links, and recent alternative versions. Also covers partial failure behavior. Complete for a composite tool with complex return.

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% with both parameters described. Description adds value by noting scoped packages are accepted (e.g., '@types/node') and that version defaults to latest if omitted. This enriches the schema definitions.

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 adding an npm package, combining deps.dev and bundlephobia. It specifies the exact purpose: answering if a package is safe/popular/small or what it costs. Distinguishes from siblings by noting NPM ecosystem only and referencing alternative tools for other ecosystems.

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: when agent asks about safety, popularity, size, or cost of npm packages. Also specifies when not to use: other ecosystems (PyPI, Maven, etc.) should use deps.dev:version directly. Provides clear context for selection.

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

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

Several tool families have unclear boundaries: ask_pipeworx_beta is explicitly identical to ask_pipeworx right now, ask_pipeworx_grounded and validate_claim both verify claims against sources, and polymarket_edges/polymarket_arbitrage/bet_research all surface prediction-market opportunities. Agents would need to read very long descriptions to distinguish overlapping intents, and would likely misroute requests.

Naming Consistency3/5

All names use snake_case, which is a consistent base, and subgroups (shodan_host*, ask_pipeworx*, polymarket_*) follow internal patterns. However, conventions mix verb-first (ask_pipeworx, validate_claim, resolve_entity) with noun-first (entity_profile, bet_research, recent_alerts), and parallel functionality is named with inverted ordering (ai_visibility_check vs scan_competitor_ai_presence).

Tool Count2/5

34 tools is above the comfortable range for a single server and the breadth feels bloated, especially with five highly niche Polymarket tools. More critically, the server is named 'Shodan' but only 3 of 34 tools are Shodan-related, so the count is badly mismatched with the stated identity.

Completeness2/5

For a server claiming to be Shodan, the surface is severely incomplete — only host lookup, search, and count are present, with no DNS, alerting, or other standard Shodan operations. For the actual Pipeworx/Polymarket domain implied by most tools, coverage is fuller but still has gaps such as no direct tool to fetch a pipeworx:// citation URI, and the memory/subscription features feel bolted on rather than integral.

Resources