Skip to main content
Glama

security-crypto

lockfile_integrity_audit

Audit npm package-lock.json (v2/v3) for non-HTTPS registry URLs, missing SHA-512 integrity hashes, and total transitive package footprint.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
textNo
filePathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It does disclose the concrete checks and therefore the shape of findings (non-HTTPS registry URLs, missing SHA-512 integrity, transitive footprint count), but it says nothing about read-only vs. mutating behavior, whether any network access occurs, or how errors on malformed lock files are surfaced.

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?

A single front-loaded sentence with the resource and the audit dimensions in order of importance. No filler, no restatement of the tool name, nothing that could be trimmed without losing information.

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?

For a low-complexity two-parameter tool with no output schema, the purpose and audit checks are adequately covered, but the unresolved input ambiguity (raw text vs. path, both optional) is exactly what an agent needs to call this correctly and is left unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and neither parameter is required, yet the description never mentions 'text' or 'filePath' at all — not which one takes precedence if both are supplied, not whether one may be omitted, not whether filePath must be absolute. The input contract is entirely undocumented.

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 ("Audit") plus a precise resource ("npm package-lock.json (v2/v3)") and enumerates the three checks performed. The resource naming inherently separates it from the sibling package_json_audit, so an agent can pick correctly without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no mention that this target is a lock file rather than package.json, yarn.lock, or an SBOM (the sbom_inspect_and_audit sibling). Usage is only inferable from the stated purpose; nothing tells the agent which conditions or prerequisites select this tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources