Skip to main content
Glama

Fencer Intel vulnerability feed

Search vulnerabilities

search

Search Fencer Intel entries (CVE, GHSA and OSV advisories merged into one entry per vulnerability). Free text in q matches ids, titles, descriptions, vendors, products and package names; structured parameters narrow the result. Each result says why it matched; when nothing matches, broader lists relaxed queries that do return results.

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

Input Schema

NameRequiredDescriptionDefault
qNoFree text, or an exact id such as CVE-2021-44228 or GHSA-jfh8-c2jp-5v3q.
kevNoOnly entries in the CISA Known Exploited Vulnerabilities catalog.
techNoTechnologies.
typeNoId family of the entry.
limitNo
vendorNoVendor or product name, matched from the start of a word ("micro" finds Microsoft), e.g. "fortinet".
packageNoExact package name, e.g. "lodash" or "org.apache.logging.log4j:log4j-core".
severityNoSeverities to include.
ecosystemNoPackage ecosystems.
exploitedNoOnly entries known exploited (KEV) or with a public exploit (Exploit-DB or Metasploit).
publishedNo2024, 2024-05, 2024-01-01..2024-03-31, >=2024-01-01, <2024-01-01, or 30d.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it discloses that each result explains why it matched and that an empty result set still returns `broader` relaxed queries. It omits result ordering, what happens on very broad queries, and any rate-limit or read-only framing, which keeps it below a 5.

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 sentences, no waste, and it front-loads the resource and data model before moving to query semantics and the empty-result fallback. Every sentence adds information an agent would otherwise have to guess.

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 an 11-parameter, all-optional search tool with no annotations and no output schema, the definition covers the data model, the two query modes, and the fallback field in results. It leaves return ordering and result shape partly implicit, though the mention of `broader` and match reasons covers the most important return-value concerns.

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 description coverage is 91%, so the schema already documents nearly every parameter, setting the baseline at 3. The description adds real meaning for `q` by enumerating the fields searched (ids, titles, descriptions, vendors, products, package names) and frames structured parameters as narrowing filters, but says nothing about the remaining ten parameters.

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 and resource ('Search Fencer Intel entries') and adds a genuinely clarifying data-model note that CVE, GHSA and OSV advisories are merged into one entry per vulnerability, which an agent could not know from the schema. It does not name or distinguish itself from siblings like get_vulnerability or list_feed, 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 Guidelines3/5

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

Gives implied routing guidance: free text in `q` for broad matching versus structured parameters to narrow, plus the fact that `broader` offers relaxed queries when nothing matches. It never states when to prefer this over get_vulnerability or list_feed, nor any exclusion conditions, so usage is inferred rather than directed.

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