Skip to main content
Glama

npm

by io.github.pipeworx-io

Get Package

get_package
Read-onlyIdempotent

Get full details for a specific package: version, description, dependencies, homepage, repository, and license. Use after search_packages to evaluate a candidate package.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesExact package name (e.g., "express", "lodash")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesPackage name
authorYesAuthor name or null
enginesYesNode/npm version requirements
licenseYesLicense type or null
versionYesLatest package version
homepageYesHomepage URL or null
keywordsYesAssociated keywords
repositoryYesRepository URL or null
descriptionYesPackage description or null
dependenciesYesProduction dependencies with version constraints
devDependenciesYesDevelopment dependencies with version constraints
peerDependenciesYesPeer dependencies with version constraints

Schema Changelog

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

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "name": "express"
+  },
+  {
+    "name": "lodash"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "author": {
+      "description": "Author name or null",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "dependencies": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "description": "Production dependencies with version constraints",
+      "type": "object"
+    },
+    "description": {
+      "description": "Package description or null",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "devDependencies": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "description": "Development dependencies with version constraints",
+      "type": "object"
+    },
+    "engines": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "description": "Node/npm version requirements",
+      "type": "object"
+    },
+    "homepage": {
+      "description": "Homepage URL or null",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "keywords": {
+      "description": "Associated keywords",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "license": {
+      "description": "License type or null",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "name": {
+      "description": "Package name",
+      "type": "string"
+    },
+    "peerDependencies": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "description": "Peer dependencies with version constraints",
+      "type": "object"
+    },
+    "repository": {
+      "description": "Repository URL or null",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "version": {
+      "description": "Latest package version",
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "version",
+    "description",
+    "license",
+    "author",
+    "keywords",
+    "homepage",
+    "repository",
+    "dependencies",
+    "devDependencies",
+    "peerDependencies",
+    "engines"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {
-    "name": "django"
-  },
-  {
-    "name": "pandas"
-  }
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "author": {
-      "description": "Package author name",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "author_email": {
-      "description": "Package author email",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "home_page": {
-      "description": "Package homepage URL",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "keywords": {
-      "description": "Package keywords",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "latest_files": {
-      "description": "Latest distribution files",
-      "items": {
-        "properties": {
-          "filename": {
-            "description": "Distribution filename",
-            "type": "string"
-          },
-          "packagetype": {
-            "description": "Package type (e.g., sdist, bdist_wheel)",
-            "type": "string"
-          },
-          "upload_time": {
-            "description": "Upload timestamp",
-            "type": "string"
-          },
-          "url": {
-            "description": "Download URL",
-            "type": "string"
-          }
-        },
-        "required": [
-          "filename",
-          "packagetype",
-          "upload_time",
-          "url"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "license": {
-      "description": "License type",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "name": {
-      "description": "Package name",
-      "type": "string"
-    },
-    "project_urls": {
-      "description": "Additional project URLs",
-      "type": "object"
-    },
-    "recent_versions": {
-      "description": "Last 10 available versions",
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "requires_python": {
-      "description": "Python version requirement",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "summary": {
-      "description": "Short package description",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "version": {
-      "description": "Latest version number",
-      "type": "string"
-    }
-  },
-  "required": [
-    "name",
-    "version",
-    "summary",
-    "author",
-    "author_email",
-    "license",
-    "requires_python",
-    "home_page",
-    "project_urls",
-    "keywords",
-    "recent_versions",
-    "latest_files"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "author": {
+      "description": "Package author name",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "author_email": {
+      "description": "Package author email",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "home_page": {
+      "description": "Package homepage URL",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "keywords": {
+      "description": "Package keywords",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "latest_files": {
+      "description": "Latest distribution files",
+      "items": {
+        "properties": {
+          "filename": {
+            "description": "Distribution filename",
+            "type": "string"
+          },
+          "packagetype": {
+            "description": "Package type (e.g., sdist, bdist_wheel)",
+            "type": "string"
+          },
+          "upload_time": {
+            "description": "Upload timestamp",
+            "type": "string"
+          },
+          "url": {
+            "description": "Download URL",
+            "type": "string"
+          }
+        },
+        "required": [
+          "filename",
+          "packagetype",
+          "upload_time",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "license": {
+      "description": "License type",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "name": {
+      "description": "Package name",
+      "type": "string"
+    },
+    "project_urls": {
+      "description": "Additional project URLs",
+      "type": "object"
+    },
+    "recent_versions": {
+      "description": "Last 10 available versions",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "requires_python": {
+      "description": "Python version requirement",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "summary": {
+      "description": "Short package description",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "version": {
+      "description": "Latest version number",
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "version",
+    "summary",
+    "author",
+    "author_email",
+    "license",
+    "requires_python",
+    "home_page",
+    "project_urls",
+    "keywords",
+    "recent_versions",
+    "latest_files"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "name": "django"
+  },
+  {
+    "name": "pandas"
+  }
+]
  5. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the description need not restate that. It adds the set of returned fields, which gives some context about behavior, but does not disclose potential edge cases (e.g., behavior for non-existent packages) or limitations beyond the schema's note about exact name. This is adequate but not richly transparent.

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 two sentences: the first states the tool's action and output fields, the second gives usage positioning. It is front-loaded and every sentence earns its place. No redundancy or filler.

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?

For a simple tool with one well-documented parameter, strong annotations, and an output schema, the description provides the necessary context: what the tool does, which fields to expect, and when to use it. There are no critical gaps that would prevent correct invocation.

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?

The sole parameter 'name' is fully described in the schema with an exact example and clarification ('Exact package name'). Schema coverage is 100%, so the description does not need to add parameter details. The description's mention of 'specific package' aligns with the schema but adds no new 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?

The description clearly states the tool's purpose: 'Get full details for a specific package' and enumerates the exact fields returned (version, description, dependencies, homepage, repository, license). It distinguishes from sibling tools like search_packages and list_versions by focusing on a single package's detailed metadata and explicitly referencing the search-then-evaluate workflow.

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 provides explicit usage guidance: 'Use after search_packages to evaluate a candidate package.' This tells the agent when to use this tool in a multi-step workflow, implying that it is not for discovery or broad queries. It clearly positions the tool relative to an alternative.

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

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

Descriptions are exceptionally detailed and differentiate tools well; the ask_pipeworx family (stable/beta/grounded), polymarket tools, and npm lookup tools each have clear separation of intent. Minor overlap exists between polymarket_edges and polymarket_arbitrage (both surface opportunities) and between discover_tools, suggest_questions, and pipeworx_trending (all aid discovery), but descriptions mostly resolve the ambiguity.

Naming Consistency3/5

All names are snake_case and several families are consistent (get_*, list_*, search_*, ask_pipeworx, polymarket_*), but the convention is inconsistent: verb-first names (resolve_entity, validate_claim, scan_dependency) coexist with noun-first or noun-only names (entity_profile, deep_research, bet_research, recent_alerts, ai_visibility_check, pipeworx_trending, polymarket_arbitrage). No clear governing pattern beyond snake_case.

Tool Count2/5

36 tools is well over the 25-tool heavy threshold, and the majority (~29) are unrelated to the server's declared 'npm' identity — they are Pipeworx data-query, prediction-market, memory, and subscription tools. Only about 7 tools (search_packages, get_package, get_version_info, list_versions, get_downloads, scan_dependency, generate_llms_txt) actually pertain to npm. The scope is a kitchen-sink mismatch with the server name.

Completeness3/5

For npm, the read-side surface is reasonably complete: search, inspect package metadata, version listings, download counts, and a dependency-safety composite check. However, there are no lifecycle operations (publish, unpublish, deprecate, set versions/tags), leaving a notable gap, and the bulk of the server's functionality (data queries, prediction bets) belongs to an entirely different domain that can't be cohesively evaluated against the npm purpose.

Resources