Skip to main content
Glama
Patrowl

PatrowlIntelMCP

Official
by Patrowl

search_cves

Search and triage CVEs using filters for risk score, EPSS, KEV catalog, exploit availability, and technology. Returns ranked results to prioritize vulnerabilities.

Instructions

Search the PatrowlIntel CVE feed with rich filters and return compact, ranked results. Use it to triage by risk (min_score / min_epss), surface KEV or exploited CVEs, or scope a vendor/technology. For the full record of one CVE, follow up with get_cve.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoOrdering; default '-score' (most risky first).-score
limitNoMax results, 1-100.
queryNoFree-text match on CVE id or summary.
is_kevNoOnly CVEs in the CISA KEV catalog.
min_epssNoMinimum EPSS exploit probability (0-1).
is_remoteNoOnly remotely exploitable CVEs.
min_scoreNoMinimum Patrowl EASM risk score (0-1).
technologyNoVendor/product substring, e.g. 'Apache' or 'Fortinet FortiOS'.
has_exploitNoOnly CVEs with at least one public exploit.
published_toNoISO date upper bound on publication.
published_fromNoISO date lower bound on publication, e.g. 2026-01-01.
Behavior3/5

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

No annotations provided, so description carries full burden. It implies a read operation (search) but does not explicitly state read-only, no side effects, or disclose rate limits or authentication needs. The mention of 'compact, ranked results' adds some behavioral context, but more specifics would be beneficial.

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?

Two sentences, front-loaded with purpose, efficient use of words. No fluff.

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?

Given no output schema and no annotations, the description covers the tool's purpose, use cases, and relationship to siblings. Could mention output format or pagination but overall complete for a search tool.

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 100%, so all parameters are documented. The description does not add extra meaning beyond the schema, which is acceptable. Baseline score of 3 is appropriate as the schema carries the load.

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?

The description clearly states it searches the PatrowlIntel CVE feed with rich filters, returning compact ranked results. It distinguishes from the sibling 'get_cve' by indicating that for full records one should use that tool.

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?

Explicitly provides use cases: triage by risk, surface KEV/exploited CVEs, scope vendor/technology, and instructs to follow up with get_cve for full records. This gives clear when-to-use and when-not-to-use guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Patrowl/PatrowlIntelMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server