Skip to main content
Glama

Ni Biashara Shelves — Africa FX, freight & compliance checks (x402)

Cybersecurity daily brief — KEV snapshot digest

get_cyber_daily_brief
Read-only

Cybersecurity daily brief — KEV snapshot digest. The vulnerability day in one call from the Ni Biashara cybersecurity shelf: band counts, the act-now total, how many records sit past CISA's own fix-by deadline, and the most recent KEV additions, computed from the current ranked snapshot at serve time. $0.5 USDC on Base. Returns the x402 URL to GET (402 → PAYMENT-SIGNATURE → delivery). Free to call this tool; payment happens on the URL.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing freshness semantics ('computed from the current ranked snapshot at serve time'), the paid-gate mechanics ('$0.5 USDC on Base', '402 → PAYMENT-SIGNATURE → delivery'), and the crucial split that the tool call itself is free while payment occurs on the returned URL. This is exactly the operational context an agent needs before invoking and then following up.

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?

Dense and front-loaded: the digest contents come before the commercial/payment details, and each sentence carries distinct information. The shelf-branding phrase ('from the Ni Biashara cybersecurity shelf') is the one bit of flavor an agent does not need.

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?

With no input parameters and no output schema, the description shoulders the return-value burden and does so by naming the four result components, plus the freshness and payment story. Minor gaps remain: it does not say how many 'most recent KEV additions' are returned, whether results are sorted, or the response format.

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?

Zero parameters, so the baseline applies; there is nothing for the description to disambiguate. The description correctly avoids inventing parameter behavior and instead spends its words on output shape and payment flow.

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?

Specific verb-and-resource framing ('daily brief — KEV snapshot digest') followed by an enumeration of exactly what the call yields: band counts, act-now total, overdue-vs-fix-by records, and recent KEV additions. That payload list implicitly separates it from per-CVE tools like search_cyber_kev, though it never names a sibling explicitly to sharpen the distinction.

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 rather than stated: 'the vulnerability day in one call' signals a summary/pulse use case, and the payment note clarifies the cost model for calling. There is no explicit when-to-use-versus-alternative guidance (e.g. brief vs. search_cyber_kev vs. get_cyber_top_priority) and no stated exclusions.

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