Skip to main content
Glama

BRAINIAC Cybersecurity Intelligence

Audit lockfile

cybersecurity-intelligence_lockfile-audit

Parse supported package lockfiles, identify dependencies and versions, then combine deps.dev and existing OSV/CISA/EPSS/NVD findings. Price $0.10 USDC. POST /api/v1/cybersecurity-intelligence/lockfile/audit. Unpaid calls return 402 and do not run.

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": {
      "lockfileContent": "<lockfileContent>"
    },
    "name": "cybersecurity-intelligence_lockfile-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
ecosystemNo
lockfileContentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations at all, the description still discloses the two traits that matter most operationally: the $0.10 USDC cost and the fact that unpaid calls return 402 and do not execute. It stops short of stating the operation is read-only/non-mutating and says nothing about rate limits or response contents.

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?

Four short sentences, front-loaded with the purpose, followed by price and failure behavior. The raw POST path is somewhat redundant for an MCP caller but is compact and costs little.

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?

There is no output schema and no annotations, so the description should say what comes back from the combined deps.dev/OSV/CISA/EPSS/NVD lookup and how ecosystem interacts with lockfileContent. It covers cost and failure mode but leaves the return shape and parameter behavior under-specified.

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%, so the description must compensate, and it does not. It never explains that lockfileContent is the raw file body or whether ecosystem is optional/auto-detected, and it does not enumerate supported formats beyond 'supported package lockfiles', leaving the enum in the schema to do all the work.

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 opens with a specific verb chain and resource: parse lockfiles, identify dependencies and versions, then combine deps.dev with OSV/CISA/EPSS/NVD findings. That clearly distinguishes it from a single-package check, though it never names the sibling tools (package-check, package-batch-check) it is meant to be chosen over.

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 is implied by the resource ('lockfiles' vs. a single package), but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent must infer that this is the bulk/project-level audit path from the sibling names alone.

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