Skip to main content
Glama

Search vulnerabilities, breaches, and advisories

search_vulnerabilities
Read-only

Search the KEVWire corpus (CISA KEV, NVD high/critical CVEs, GitHub advisories, national CERTs, security reporting, editorial records) by words, technology, kind or exploitation. Use it to answer "is X affected" or "what is known about Y"; for a known ID use get_record, and for a plain "what is being exploited lately" list use list_recent_exploited. Default order is "urgent": the last 30 days first, then known exploitation, CVSS 9+, breaches. Results are paged (see hasMore and offset) and include source URLs to cite.

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": "search_vulnerabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
sortNo
limitNo
queryNoWords to match, e.g. "php rce", a CVE ID, a product, or an event name like "PHP2Shell".
offsetNo
technologiesNoTechnology labels, e.g. ["Microsoft Windows", "PHP"]. Matches any.
known_exploited_onlyNoOnly records in the CISA Known Exploited Vulnerabilities catalog.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint=false; the description goes well beyond by disclosing the default ranking algorithm ('urgent': last 30 days, known exploitation, CVSS 9+, breaches), the pagination contract (hasMore + offset) and that results carry citable source URLs. This is exactly the behavioural context an agent cannot get from the structured fields.

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?

Front-loaded with purpose, then usage, then defaults, then return behaviour — a sensible ordering with no filler sentences. The corpus enumeration in the first sentence is long, though each item does add real scope information.

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 7-parameter, zero-required search tool with no output schema, the description supplies result shape (paged, hasMore/offset, source URLs) and default ordering, which is the information an agent most needs. Remaining gaps are minor: unenumerated kind values and no note on what an empty result set looks like.

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 only 43%, and the description compensates for the biggest gap by defining what the 'urgent' default sort actually does and that offset/hasMore drive paging; the schema itself documents query, technologies and known_exploited_only. It still leaves the kind enum values and the limit cap (max 50) unexplained, so it is strong but not complete.

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?

Specific verb (search) plus the exact resource and corpus boundaries ('KEVWire corpus: CISA KEV, NVD high/critical CVEs, GitHub advisories, national CERTs...'), and the matchable dimensions (words, technology, kind, exploitation). It is clearly distinguishable from get_record and list_recent_exploited without opening any schema.

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

Usage Guidelines5/5

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

Gives concrete use cases in the user's own phrasing ('is X affected', 'what is known about Y') and explicitly routes two neighbouring intents elsewhere: known ID -> get_record, recent-exploitation list -> list_recent_exploited. Nothing about selection is left to inference.

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