Skip to main content
Glama
MShekow

package-version-check-mcp

by MShekow

get_latest_tool_versions

Retrieve the latest stable versions of development and DevOps tools not covered by language package managers, enabling accurate version pinning in configuration files.

Instructions

Get the latest stable versions of tools supported by mise-en-place.

This tool fetches the latest stable version of development and DevOps tools that are NOT part of language ecosystems like PyPI or NPM. For language ecosystem packages (including Terraform providers and modules), use the get_latest_package_versions tool instead.

Use this tool to determine the latest versions of tools like:

  • gradle: Pin the Gradle version in distributionUrl in gradle-wrapper.properties (e.g., distributionUrl=https://services.gradle.org/distributions/gradle-8.5-bin.zip)

  • maven: Pin the Maven version in distributionUrl in maven-wrapper.properties (e.g., distributionUrl=https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.6/apache-maven-3.9.6-bin.zip)

  • terraform: Pin terraform.required_version in a file like version.tf or versions.tf (e.g., terraform { required_version = "~> 1.6.0" })

  • kubectl: Pin the version in a download URL called with curl or wget in a Dockerfile (e.g., RUN curl -LO https://dl.k8s.io/release/v1.28.0/bin/linux/amd64/kubectl)

  • azure: Pin Azure CLI version in download URL (e.g., curl -LO https://azurecliprod.blob.core.windows.net/releases/azure-cli-2.50.0.tar.gz)

To see all available tools, use the get_supported_tools tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tool_namesYesA list of tool names (e.g., ["terraform", "gradle", "kubectl"])

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
lookup_errorsYes
Behavior4/5

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

Description discloses it returns stable versions for a specific set of tools, and no side effects are implied. Without annotations, it adequately covers behavioral expectations.

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?

Front-loaded with purpose, well-organized with examples, but contains some lengthy details that could be condensed.

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?

Comprehensive for a simple tool with output schema; includes scope differentiation, usage guidance, and reference to sibling for full list.

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 covers 100% of parameters; description adds value by providing concrete example tool names, enhancing understanding of valid inputs.

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 fetches latest stable versions of non-language-ecosystem tools, and distinguishes from sibling get_latest_package_versions.

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 (for tools not in language ecosystems) and when not to (use get_latest_package_versions for ecosystem packages), with practical examples.

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