Skip to main content
Glama
MShekow

package-version-check-mcp

by MShekow

get_latest_package_versions

Check the latest stable versions of packages from NPM, PyPI, NuGet, Maven, Go, PHP, Ruby, Rust, Swift, Dart, Docker, Helm, and Terraform. Returns version info and errors for each package request.

Instructions

Get the latest versions of packages from various ecosystems.

This tool fetches the latest version information for packages from NPM, PyPI, NuGet, Maven/Gradle, Go modules, PHP/Packagist, Ruby gems, Rust crates, Swift packages, Dart packages, Docker, Helm, Terraform modules and Terraform providers. It returns both successful lookups and any errors that occurred.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packagesYesA list of package version requests with: - ecosystem: "npm", "pypi", "nuget", "maven_gradle", "go", "php", "rubygems", "rust", "swift", "dart", "docker", "helm", "terraform_provider", or "terraform_module" - package_name: The name of the package (e.g., "express", "requests", "Newtonsoft.Json") For Maven/Gradle, use format "[registry:]<groupId>:<artifactId>" (e.g., "org.springframework:spring-core" for Maven Central, "maven.google.com:com.google.android.material:material" for Google Maven) For Go, use the absolute module identifier (e.g., "github.com/gin-gonic/gin") For PHP, use the Packagist package name in "vendor/package" format (e.g., "monolog/monolog", "laravel/framework") For RubyGems, use the gem name (e.g., "rails", "devise") For Rust, use the crate name (e.g., "serde", "tokio") For Swift, use the GitHub URL (e.g., "https://github.com/owner/repo.git" or "github.com/owner/repo.git") - only github.com is supported For Dart, use the package name from pub.dev (e.g., "flutter", "http") For Docker, this must be fully qualified (e.g., "index.docker.io/library/busybox") For Helm, use one of these formats: - ChartMuseum: "https://host/path/chart-name" (fetches from index.yaml) - OCI: "oci://host/path/chart-name" (queries OCI registry tags) - version_hint: (optional) For Docker and Helm OCI, used as a tag compatibility hint (e.g., "1.2-alpine") to find the latest tag matching the same suffix pattern. For NPM/PyPI/NuGet/Maven/ChartMuseum/Go/PHP/RubyGems/Rust/Swift/Dart, not used.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
lookup_errorsYes
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions error handling but does not disclose whether the tool is read-only, requires authentication, or has rate limits. The description lacks detail on idempotency and side effects.

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?

The description is front-loaded with the core purpose and efficiently lists ecosystems without extraneous detail. It is moderately long but each sentence contributes value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity and the presence of an output schema, the description adequately covers input handling and error reporting. However, it does not explain the output structure or preconditions, leaving some gaps.

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 input schema has 100% coverage with detailed descriptions per parameter, including formatting examples. The main description adds little beyond listing ecosystems, so it meets the baseline for high schema coverage.

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: getting latest versions of packages from various ecosystems. It lists supported ecosystems and indicates return of both successes and errors, distinguishing it from sibling tools like get_github_action_versions_and_args.

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?

The description implies use for package version lookups but provides no explicit when-to-use or when-not-to-use guidance. It does not contrast with sibling tools or mention exclusion criteria, leaving the agent to infer from context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MShekow/package-version-check-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server