Skip to main content
Glama

Search CVEs by concept, keyword or seed CVE

search_vulns
Read-only

Search the CVE corpus — one entry point, three retrieval modes picked from your arguments:

  • query= a concept / technique / weakness (e.g. "SSO SAML assertion replay", "deserialization gadget chain", "server-side request forgery cloud metadata"). By default it FUSES full-text keyword search AND semantic mechanism-search, so you don't have to guess whether your phrasing is lexical or conceptual. order='relevance' = keyword only; order='similarity' = semantic only; order='severity' = fuse then rank P1>P4.

  • cve_id= a seed CVE (e.g. "CVE-2021-44228") -> its mechanism-siblings across OTHER products (the "what else looks like this?" move).

  • days= and/or product= (with NO query) -> the recent high-risk window (KEV / P1-P2 / high-EPSS); product= is CPE-name-resolved and each hit carries match.products. "Recent" = published in the window OR added to CISA KEV in it (an old CVE newly confirmed exploited counts); each hit says which (in_window / kev_added).

A recency phrase inside query ("this week", "in the last 30 days", "today") is read as days=; interpreted_as says how the query was read.

Returns ranked cards (each with priority/KEV/EPSS/CWE) + total_matches for coverage; the 'mode' field reports which retrieval ran. You decide which matches matter. (For one product's version-resolved vulns use check_technology, for a whole stack hunt_plan; for how bugs like this were FOUND in disclosed reports use find_attack_approaches.)

Args: query: free-text concept / keyword / CWE. cve_id: seed CVE for semantic mechanism-sibling search. cwe: optional weakness filter, e.g. "CWE-502" or "502". days: window in days: published OR added to CISA KEV within it. product: product filter for the recent-window mode (CPE-name-resolved, carries provenance). order: relevance | similarity | severity (default: fused when query is text). limit: max results (default 20).

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_vulns"
  }
}

Input Schema

NameRequiredDescriptionDefault
cweNo
daysNo
limitNo
orderNo
queryNo
cve_idNo
productNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description nonetheless adds genuinely non-obvious behavior: default fusion of lexical and semantic search, what order values switch off, that recency phrases inside query are parsed into days=, that "recent" includes KEV-added older CVEs with in_window/kev_added flags, and that mode/interpreted_as are reported back. That is real value beyond the annotations, though return shape and ranking mechanics stay high-level.

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 the three-mode framing, then details, then returns, then sibling routing — a sensible funnel. It is long, and the trailing Args block partially duplicates the body (query, cve_id, days), costing some redundancy, but nearly every line carries operative information.

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?

No output schema exists, yet the description names the returned fields (ranked cards with priority/KEV/EPSS/CWE, total_matches, mode), which is exactly what an agent needs to interpret results. Combined with mode-selection rules and sibling routing, nothing material for correct invocation is 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%, so the description carries the full burden and does document all seven parameters in the Args block. It adds real meaning for cwe (accepts "CWE-502" or "502"), days (published OR KEV-added), product (CPE-name-resolved, carries provenance), and order (enumerates the three values and their effects), though limit and query entries are close to restating the field names.

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 verb and resource ("Search the CVE corpus") and immediately decomposes it into three named retrieval modes keyed to which argument is supplied. It also names the sibling tools it is not (check_technology, hunt_plan, find_attack_approaches), so an agent can route 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 explicit when-to-use rules per mode: query for concept/keyword, cve_id for mechanism-siblings "across OTHER products", days/product with no query for the recent high-risk window. It also states the exclusion cases by redirecting to check_technology, hunt_plan and find_attack_approaches.

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.