Skip to main content
Glama

UAI x402 Security Tools

dependency-cve-scan

Scan package.json or lockfile text for dependency CVE risk signals — outdated lodash/axios, deprecated packages, wildcard pins, risky postinstall scripts, and embedded secrets. (REST equivalent: POST /api/v1/dependency-cve-scan, $0.05)

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": {
      "manifestText": "<manifestText>"
    },
    "name": "dependency-cve-scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
manifestTextYespackage.json, lockfile, or yarn.lock contents

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Only a title annotation is supplied, so the description carries most of the burden. It usefully discloses accepted input forms (package.json, lockfile, yarn.lock), the detection categories, and a concrete cost ($0.05) plus the REST endpoint. It does not state that the operation is read-only, whether the input is stored, or what the response shape looks like.

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?

One front-loaded sentence with the resource and detection list, followed by a compact parenthetical for endpoint and price. Nothing is padded, though the pricing/REST aside is secondary information placed inline with the primary purpose statement.

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 one-parameter scan with no output schema, the enumerated risk categories effectively signal what kinds of findings come back, and the input formats are covered. A brief note on whether the scan is non-destructive or what a result entry looks like would close the remaining gap.

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 coverage is 100% for the single parameter, and the schema description already says "package.json, lockfile, or yarn.lock contents." The description's mention of the same formats adds essentially nothing beyond the structured field, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ("Scan package.json or lockfile text for dependency CVE risk signals") and enumerates the concrete checks performed (outdated lodash/axios, deprecated packages, wildcard pins, postinstall scripts, embedded secrets). That is far more informative than a name restatement. It does not, however, distinguish itself from siblings like secret-scan or cve-lookup, despite overlapping with both.

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 guidance and no routing to or away from alternatives such as secret-scan (which also covers secrets) or cve-lookup. The required manifestText parameter implies the input context, but the agent is left to infer when this tool is the right choice.

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