Skip to main content
Glama
Sign In

Tlacuilo

by io.github.mastercobeos
OverviewDiscussionsAdmin

deps_check

deps_check
Read-only

Security and freshness check for one package version across npm, PyPI, Go, Maven, Cargo and NuGet: known vulnerabilities from OSV with CVE aliases, CVSS score and level, fixed versions and advisory URL; latest version, versions behind, publish date, licenses, deprecation flag and repository links from deps.dev; and a one-word verdict (ok, outdated or vulnerable). Version defaults to the latest release. Price: $0.005 USDC per call (x402).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "deps_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesPackage name, e.g. lodash, @types/node, requests, github.com/gin-gonic/gin, org.apache.logging.log4j:log4j-core
versionNoExact version to check (default: latest)
ecosystemNonpm (default), pypi, go, maven, cargo or nuget

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the readOnlyHint annotation, the description discloses the data sources (OSV and deps.dev), the exact payload contents including CVE aliases, CVSS score/level, fixed versions, advisory URL and verdict vocabulary, and — importantly — the metered cost of $0.005 USDC per call via x402. Pricing and payment-scheme disclosure is genuinely useful context an agent cannot obtain from annotations or schema; only rate limits and failure behavior are absent.

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?

Effectively two sentences: the first is dense but front-loads the purpose and then packs return-value detail, and the second carries the price. Nothing is wasted, though the single long clause listing output fields is harder to scan than a short bulleted structure would be.

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?

With no output schema present, the description carries the burden of describing results and does so in detail — vulnerability data, version staleness, publish date, licenses, deprecation flag, repository links, and the final verdict. An agent knows what it will get back and what it will cost before calling.

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 the schema already documents all three parameters including the ecosystem list and the latest-version default. The description restates the default behavior and enumerates ecosystems, adding confirmation but no format or syntax detail beyond what the schema provides — the baseline 3 fits.

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 — a security and freshness check for one package version — and enumerates the exact ecosystems covered (npm, PyPI, Go, Maven, Cargo, NuGet). The scoping to 'one package version' implicitly distinguishes it from a broader audit-style sibling without needing to name one.

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?

Usage context is implied by 'Security and freshness check for one package version' and the note that version defaults to the latest release. However, there is no explicit when-to-use/when-not-to-use guidance and no routing statement pointing at an alternative tool for multi-package or project-wide scans.

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

All Tlacuilo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources