Agent Tools

package_advisories

Free tier: 25 calls/day per IP with header X-Free-Call: 1 (or ?free=1), then pay per call. Check a package before installing it: known vulnerabilities for one npm, PyPI, cargo, Go or Maven package version (OSV.dev), fixed-in version, latest version and release date, licence, deprecated flag, and a safe, caution or avoid verdict with reasons. Version defaults to latest. Price $0.005 USDC per call via x402. Example output: {"ecosystem":"npm","name":"lodash","version":"4.17.20","version_checked":"requested","verdict":"avoid","reasons":["5 known advisories affect this version (worst: high)","a newer version exists"],"vulnerabilities":{"count":5,"by_severity":{"HIGH":2,"MODERATE":3},"items":[{"id":"GHSA-29mw-wpgm-hmr9","

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": {
      "ecosystem": "<ecosystem>",
      "name": "<name>"
    },
    "name": "package_advisories"
  }
}

Input Schema

Name	Required	Description
`free`	No	Use the shared free allowance (25 successful calls per IP per UTC day across eligible tools). Defaults to false.
`name`	Yes	Package name, e.g. lodash or requests (maven: group:artifact)
`version`	No	Optional. Defaults to the latest version
`ecosystem`	Yes	Package ecosystem

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

addedInput schema / properties / free

Added value: +{
+  "description": "Use the shared free allowance (25 successful calls per IP per UTC day across eligible tools). Defaults to false.",
+  "type": "boolean"
+}

AddedOct 30, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and mostly does so: it discloses the free allowance (25 successful calls per IP per UTC day), the pay-per-call price ($0.005 USDC via x402), the auth/header mechanism (X-Free-Call: 1 or ?free=1), the upstream data source (OSV.dev), and the verdict taxonomy with reasons. It omits failure behavior (unknown package, unsupported version), whether results are cached, and any rate limiting beyond the free tier.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core sentence is dense and informative, but the description is front-loaded with billing mechanics before saying what the tool does, repeats pricing twice, and ends with an example output that is truncated mid-JSON string, which is wasted and potentially confusing text.

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, so the description is the only source for return shape, and it relies on an example payload that is cut off before the vulnerabilities array closes, leaving the return contract only partially specified. Inputs, defaults, verdict semantics, and pricing are adequately covered for a 4-parameter tool, but the malformed example blunts the main reason to include it.

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 the baseline is 3, but the description adds meaning beyond the schema: it surfaces the header/query-string alternative (?free=1) that the boolean 'free' property does not mention, and reinforces that version is optional and defaults to latest. The ecosystem list is simply restated from the enum, adding no new information.

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 states a specific verb and resource: 'Check a package before installing it' and 'known vulnerabilities for one npm, PyPI, cargo, Go or Maven package version (OSV.dev)', and enumerates the returned data (fixed-in version, latest version, licence, deprecated flag, verdict). That is far more precise than the bare name. It does not, however, name or differentiate against the obvious siblings dependency_audit and manifest_scan, so an agent must infer whether this is the single-package variant of those.

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 phrase 'Check a package before installing it' gives a clear situational trigger, and 'Version defaults to latest' tells the agent it can omit version. There is no explicit when-not guidance and no named alternative for bulk/manifest scans, so routing between this and dependency_audit/manifest_scan is left to the agent.

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

All Agent Tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?