Skip to main content
Glama

Fencer Intel vulnerability feed

List a feed

list_feed

Newest entries of a feed, the same as the /feed endpoint, ordered by listed: when the entry became news here (its publish date, or later if it reached us late or turned critical later). filter: critical = in CISA KEV, or CISA SSVC exploitation "active", or CVSS 9+ in a listed technology (WordPress plugins and themes excepted; WordPress itself counts), or CVSS 7+ with EPSS ≥ 0.1; kev = in CISA KEV (ordered by date added). An entry must match any value of a field and every field given.

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

Input Schema

NameRequiredDescriptionDefault
techNoTechnologies.
limitNo
cursorNonext_cursor from a previous call.
filterNoFeed filters.
vendorNoVendor or product name, matched from the start of a word, e.g. "fortinet" or "exchange server".
ecosystemNoPackage ecosystems.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses the sort key and its edge cases, the exact boolean matching rule ('any value of a field and every field given'), and the full definition of each filter value including exceptions (WordPress plugins/themes excluded, WordPress core counted). It does not cover pagination behavior, result shape, or any rate/permission constraints, which keeps it below 5.

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?

Purpose and ordering are front-loaded, and the long filter clause is dense but each clause defines a condition the agent cannot get from the schema. The reference to 'the same as the /feed endpoint' is mild filler for an agent that has no HTTP context, and the definition reads as one run-on block rather than being split into scannable parts.

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?

For a 6-parameter read tool with no annotations and no output schema, the description covers filtering and ordering well but leaves the return shape entirely unspecified — the agent is not told what an entry looks like, nor is cursor pagination behavior mentioned despite `cursor` being a parameter. Adequate to call correctly, but not fully complete for interpreting results.

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 83%, so the baseline is 3; the description earns an extra point by defining what `filter` values actually mean operationally (KEV membership, SSVC exploitation active, CVSS/EPSS thresholds, WordPress caveats) and by stating the cross-field AND / within-field OR matching semantics that the schema does not convey. It adds little for `tech`, `ecosystem`, `vendor`, `limit`, or `cursor`, which the schema already documents.

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?

The description states the resource and its ordering precisely: 'Newest entries of a feed ... ordered by `listed`', and clarifies what `listed` means (publish date, or later if the entry reached the feed late or turned critical). What a 'feed' contains is only implied (vulnerability entries), and no sibling tool is named to distinguish this from `search` or `check_stack`, so it is clear but not differentiated.

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?

Usage is implied through the detailed `filter` semantics (critical vs kev) and the ordering rule, so an agent can infer this is for browsing/streaming recent entries with triage filters. However, there is no explicit when-to-use statement, no exclusions, and no pointer to `search` or `get_vulnerability` for lookup-style queries.

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