Skip to main content
Glama
texWoW

unripe

by texWoW
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Check lockfiles for versions that are too new

check_lockfiles
Read-onlyIdempotent

Scans lockfiles in a directory and reports locked versions younger than a minimum age or with unknown age, optionally limited to changes since a git ref.

Instructions

Check every lockfile under a directory (package-lock.json, pnpm-lock.yaml, yarn.lock, bun.lock, deno.lock, uv.lock, poetry.lock, requirements.txt, Cargo.lock, go.mod, composer.lock, Gemfile.lock, packages.lock.json, gradle.lockfile, pubspec.lock, Podfile.lock, Package.resolved, .terraform.lock.hcl, conan.lock, renv.lock, mix.lock, flake.lock, MODULE.bazel.lock, vcpkg.json and more) and report every locked version that is younger than the minimum age or whose age is unknown. Set since to a git ref, like origin/main, to check only what changed since then.

Input Schema

NameRequiredDescriptionDefault
pathNoA directory or lockfile. Defaults to the current directory.
sinceNoOnly check versions added since this git ref, like origin/main or HEAD.
min_ageNoOverride the minimum age, like 72h, 3d or 1w. Leave out to use the project's policy.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, open-world behavior. The description adds meaningful context beyond annotations: it recursively checks every lockfile, flags versions younger than the minimum age or with unknown age, and supports git-ref-based filtering.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first sentence, but the extensive parenthetical list of lockfile types is long and ends with 'and more,' reducing its precision. It is functional but not tightly concise.

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

Completeness4/5

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

Covers the core behavior, supported file types, age threshold, unknown-age handling, and git-ref filtering. With no output schema, it could say more about report format or error behavior, but it is sufficient for an agent to invoke the tool correctly.

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 description coverage is 100%, so all three parameters are already documented. The description reinforces the meaning of 'since' and 'min_age' but adds little syntax or format detail beyond the schema baseline.

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?

States a specific verb and resource: checks lockfiles under a directory and reports locked versions that are too new or have unknown age. The supported-file list makes the scope concrete and distinguishes it from a package-level check tool.

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?

Explains one useful invocation pattern: use 'since' with a git ref to limit checks to changed versions. However, it does not explicitly say when to use this tool versus check_package or cooldown_settings, nor does it provide when-not guidance.

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

Deploy Server

Other Tools