Skip to main content
Glama

security-crypto

package_json_audit

Audit an npm package.json manifest for unpinned git/http dependencies, risky preinstall/postinstall lifecycle hooks, and missing engines/exports.

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": "package_json_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
filePathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet it only lists what gets checked. It does not state that the audit is purely static/read-only with no network or install side effects, does not mention severity or result shape, and gives no hint about whether the file is read or the package is executed.

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 no filler, and the critical scope (which manifest, which risk classes) comes first. Nothing is repeated or wasted.

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?

For a small two-input audit tool with no output schema, the check coverage is stated clearly enough to know what the tool reports on. The remaining gap is the dual input mode, which the description leaves entirely to the undocumented schema.

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 coverage is 0% for two parameters, text and filePath, and the description mentions neither. Nothing explains whether to supply raw manifest content or a path, what happens if both are given, or what format the path should take, so the agent gets no help choosing between the two input modes.

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?

Names a specific verb and resource ('Audit an npm package.json manifest') and enumerates the exact classes of findings it produces: unpinned git/http dependencies, risky preinstall/postinstall hooks, and missing engines/exports. That scope cleanly separates it from lockfile_integrity_audit and sbom_inspect_and_audit, which operate on different artifacts.

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?

The description never says when to reach for this tool or what the alternatives are, despite having closely related siblings in the audit family. An agent must infer from the name alone whether to use this or a lockfile/SBOM audit.

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