Skip to main content
Glama
io.github.kushvinth/crowbar

io.github.kushvinth/crowbar

cb_advisory

Query OSV and GHSA advisories by ecosystem or exact package name to retrieve introduced and fixed version ranges for vulnerability matching.

Instructions

OSV/GHSA advisories with introduced/fixed version ranges. Filter by ecosystem (npm, PyPI, Go, Maven, NuGet, RubyGems, crates.io, Packagist, Debian, Alpine) or exact package name.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cb_advisory"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
packageNo
ecosystemNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the meaningful payload trait that advisories include introduced/fixed version ranges, which tells the agent what it will get back, but it says nothing about pagination, truncation at the default limit of 30, or whether lookups are pure reads.

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?

Two sentences, front-loaded with what the tool returns before the filtering options. The long ecosystem list is bulky but earns its place because the schema supplies no enum. Nothing redundant.

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?

With no annotations, no output schema, and four undocumented parameters, the definition should say more. The returned-record shape and ecosystem values are covered, but the role of query versus package, the meaning of limit, and expected call patterns are absent.

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 0%, so the description must compensate and it only partly does. It helpfully enumerates valid ecosystem values (npm, PyPI, Go, Maven, NuGet, RubyGems, crates.io, Packagist, Debian, Alpine) where the schema has no enum, and clarifies that package is an exact-name match, but query and limit are left entirely unexplained.

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?

States a specific verb+resource: OSV/GHSA advisories, and adds the distinguishing content detail that records carry introduced/fixed version ranges. It is clearly a different resource from siblings like cb_cve or cb_attack, but the description never explicitly names or contrasts an alternative, so it stops short of a 5.

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?

It explains how to narrow results (ecosystem or exact package name) but never says when this tool is the right choice versus cb_cve or cb_search, nor when it is not appropriate. The agent must infer usage context from the name alone.

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