Crypto, web, finance and app data tools

Package Vulnerabilities (OSV)

package_vulnerabilities

Known security vulnerabilities for an open-source package from OSV (GitHub advisories, PyPA, RustSec, Go): id, CVE aliases, summary, severity, fixed versions, for all versions or one version. Ecosystems: npm, PyPI, Go, Maven, crates.io, RubyGems, NuGet, Packagist. Use before installing or upgrading.

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>"
    },
    "name": "package_vulnerabilities"
  }
}

Input Schema

Name	Required	Default
`package`	Yes
`version`	No
`ecosystem`	No	npm

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 22, 2026

TDQS

A4.3/5.0

Behavior3/5

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

No annotations are supplied, so the description bears the full behavioral burden. It usefully discloses the upstream sources and that results cover either all versions or a single one, but says nothing about rate limits, caching, or how unknown packages/ecosystems are handled. The read-only nature is only implied by the lookup framing.

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?

Three compact clauses: what is returned, which ecosystems, when to call it. No filler, and the core return content is front-loaded ahead of the ecosystem list and usage hint.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description need not explain the return shape, and it still names the key fields for scannability. For a three-parameter read-only lookup with no annotations, the source, scope, and ecosystem coverage leave nothing material missing.

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 description coverage is 0%, but the description compensates substantially: it spells out the ecosystem vocabulary (npm, PyPI, Go, Maven, crates.io, RubyGems, NuGet, Packagist), which the schema lacks as an enum, and clarifies that omitting the version returns vulnerabilities for all versions. It does not give naming/format conventions (e.g. scoped npm packages) or confirm npm as the default.

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?

States a specific resource (known security vulnerabilities) and a specific source (OSV, aggregating GitHub advisories, PyPA, RustSec, Go), then enumerates the returned fields and the supported ecosystems. The package-scoped framing distinguishes it implicitly from the CVE-id-scoped sibling 'cve_details' and from manifest lookups like 'npm_package'/'pypi_package'.

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?

"Use before installing or upgrading" gives a concrete trigger point for invoking the tool. It does not, however, state when to prefer a sibling such as cve_details for a specific advisory ID, nor what to do if the package/ecosystem pair is unknown.

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

All Crypto, web, finance and app data 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?