Skip to main content
Glama

Packagephobia

by io.github.pipeworx-io

Size

size
Read-onlyIdempotent

Return the publish size and full install size (including dependencies) in bytes for an npm package name and optional version via packagephobia.com.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packageYesnpm package name (scoped allowed)
versionNoSpecific version (default latest)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
packageNonpm package name
versionNoPackage version
installSizeNoInstall size in bytes
publishSizeNoPublish size in bytes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so description adds value by explaining the tool queries packagephobia.com and returns sizes in bytes including dependencies. No contradictions with annotations.

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?

Single sentence with no redundancy. Front-loaded with key information about what is returned and from where.

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?

Given the simple tool with 2 well-documented parameters, rich annotations, and an output schema (exists), the description fully covers what the tool does without missing critical information.

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?

Schema coverage is 100%, with both parameters having descriptions. The description adds minimal parameter-specific meaning beyond restating that version is optional and default is latest. The mention of 'packagephobia.com' provides external context but not parameter semantics.

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 explicitly states verb 'Return', resource 'publish size and full install size', and source 'npm package name and optional version via packagephobia.com'. It clearly distinguishes itself from sibling tools, none of which perform this specific function.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description does not provide explicit guidance on when to use this tool versus alternatives. While the tool's purpose is clear, there is no mention of prerequisites, when to avoid, or related tools. However, given its unique function, the need for such guidance is lower.

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

All Packagephobia 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.8/5.0
Disambiguation2/5

Several near-overlapping query tools exist: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route to the same underlying catalog, and ask_pipeworx_beta is currently described as identical to ask_pipeworx. The Polymarket tools (bet_research, polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, polymarket_edge_tracker) also heavily overlap and rely on lengthy descriptions to keep them apart.

Naming Consistency3/5

The set is uniformly snake_case and generally readable, but conventions are mixed: verb_noun (resolve_entity, suggest_questions), noun_verb (bet_research, ai_visibility_check), noun_adj (pipeworx_trending, recent_changes), and bare verbs (size, forget, recall) all appear. Variant suffixes like ask_pipeworx_beta and ask_pipeworx_grounded add further unpredictability.

Tool Count2/5

32 tools exceeds the 'too many' threshold and spans unrelated domains: package size, general data research, prediction markets, memory, and subscription management. The set would feel more coherent at roughly half the count, with several query and Polymarket tools consolidated.

Completeness3/5

For the dominant data-research purpose, the surface is reasonably complete: querying, grounded verification, deep research, entity resolution, entity profiles, comparisons, claim validation, and discovery are all covered. However, the server's stated identity ('Packagephobia') is nearly absent—only `size` and `scan_dependency` address package sizing—so the namesake domain is thin while unrelated domains are overbuilt.

Resources