Skip to main content
Glama
Sign In
MCP OSINT Server

MCP OSINT Server

by abrahamhl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

cve_brief

Fetch a prioritized vulnerability brief, filtered by watchlist and item limit, to surface the security risks that need attention first.

Instructions

Get prioritized vulnerability brief

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

Input Schema

NameRequiredDescriptionDefault
langNo
max_itemsNo
watchlistNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and supplies almost nothing: 'Get' implies read-only, but there is no mention of rate limits, auth requirements, what 'prioritized' ordering means, or whether the watchlist parameter alters the result set. For a tool with zero annotation coverage this leaves the agent guessing.

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?

A single front-loaded phrase with zero filler; nothing is redundant or buried. It is efficient, though efficiency here comes at the cost of the missing detail scored in the other dimensions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Three parameters, no annotations, and no output schema, yet the description is eight words long. It omits what the brief contains, how items are prioritized, and how watchlist and max_items shape the response — an agent cannot call this confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, so the description must compensate and it does not mention lang, max_items, or watchlist at all. 'lang' and 'max_items' are self-describing from their names, but the semantics of 'watchlist' (CVE IDs? products?) and the enum's effect are entirely undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb ('Get') and a resource ('vulnerability brief') with a modifying adjective ('prioritized'), so it is not a pure tautology. However, 'brief' is undefined — an agent cannot tell what the payload contains or what 'prioritized' is relative to. Siblings (sanctions_screen, ioc_search) are unrelated domains, so no differentiation is needed there, but the purpose remains vague.

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

Usage Guidelines2/5

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

No guidance at all on when to call this versus the sibling tools or versus any other retrieval path. There is no context, prerequisite, or exclusion stated. The only inference available is that a 'brief' is a summary-shaped read.

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

Deploy Server

Other Tools