Skip to main content
Glama

Software risk check

software_risk_check

Should I install this package version? Known vulnerabilities for one package@version from OSV.dev (GitHub, PyPA, Go and RustSec advisories), whether any is on CISA's Known Exploited Vulnerabilities list, and the version that fixes each, with the licence and credit for every source. Absence of advisories is not proof of safety. $0.003 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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": {
      "package": "<package>",
      "ecosystem": "<ecosystem>",
      "version": "<version>"
    },
    "name": "software_risk_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
packageYespackage name, e.g. lodash
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.
versionYesexact version, e.g. 4.17.15
ecosystemYesnpm, PyPI, Go, crates.io, Maven, NuGet, RubyGems, Packagist, Hex or Pub

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations at all, the description must carry the full behavioral burden, and it does a lot: it discloses the data provenance, the interpretation caveat ('absence of advisories is not proof of safety'), the price ($0.003 per call), and the accepted payment rails. What is missing is any sense of response shape or latency — though with no output schema that gap is partly unavoidable.

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?

The decision question and the data scope are front-loaded, followed by the caveat and then the commercial terms — a sensible order. The enumeration of payment networks (Arc, Base, Solana, X1) is the one clause that runs long for its decision value, but nothing is redundant.

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 4-parameter query tool with no annotations and no output schema, the description covers what the agent needs to decide and to invoke: inputs, evidence sources, caveat, price, and the two-call payment handshake. The lack of a described return structure for the advisory list itself is the remaining gap.

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

Parameters4/5

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

Schema coverage is 100%, so package/version/ecosystem are already documented and the baseline would be 3. The description earns extra credit by explaining the fourth parameter's protocol: `payment` is a signed x402 payload obtained by first calling without it, which is meaning the schema does not convey on its own.

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?

It leads with a concrete question the agent can act on ('Should I install this package version?') and then names the exact resource: known vulnerabilities for one package@version from OSV.dev, CISA KEV membership, and fix versions. The named advisory sources (GitHub, PyPA, Go, RustSec) separate it cleanly from nearby siblings like arc_token_check, drug_safety_card or company_check, which cover different risk domains.

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

Usage Guidelines4/5

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

The framing question tells the agent precisely the decision context this tool serves, and the payment flow is spelled out as an ordered procedure (call without `payment` for terms, sign, call again with `payment`). It does not name an alternative tool or say when not to use it, which keeps it short of a 5.

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