Skip to main content
Glama

Lilambd Data for Agents

cve-priority

Which vulnerabilities in this vendor's products should I patch first?. Joins NVD CVE records (CVSS), FIRST EPSS exploit probability and the CISA Known Exploited Vulnerabilities catalog for one vendor (optionally one product) and returns a patch order with tiers, KEV due dates and a summary (expected exploited count, top CWEs). Ranking computed by Lilambd. Routes: /answer (vendor*, product, days, limit, offset); /kev-recent (days, vendor, limit). Paid $0.5 USDC per call via x402 (_meta["x402/payment"]); set sample=true for a free 3-row preview.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "route": "<route>"
    },
    "name": "cve-priority"
  }
}

Input Schema

NameRequiredDescriptionDefault
routeYesOne of: /answer, /kev-recent. Replace {placeholders} with a value, e.g. /search or /HND.
paramsNoQuery parameters, e.g. {"q":"tokyo","limit":"50"}
sampleNoFree preview, max 3 rows

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations present, the description carries the full behavioral burden and does so: it discloses that calls cost $0.5 USDC via x402, names the exact _meta["x402/payment"] field, offers a free 3-row sample mode, and describes the return shape (tiers, KEV due dates, expected exploited count, top CWEs). This is precisely the kind of cost/auth/return context an agent needs before invoking a paid endpoint.

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?

The answer-shaped question is front-loaded, then data sources, ranking provenance, routes and payment terms follow in a logical order. It is dense — the payment/pricing sentence is packed — but nearly every clause (routes, x402 field, sample preview) carries information an agent must act on.

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

Completeness5/5

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

There is no output schema, yet the description summarizes the return contents (patch order with tiers, KEV due dates, summary metrics), explains the ranking source (Lilambd), and covers payment mechanics and the free preview. Nothing material is missing for an agent deciding whether and how to call it, even with nested params and no annotations.

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 100%, so baseline is 3, and the description adds real value by listing the per-route query parameters (/answer: vendor*, product, days, limit, offset; /kev-recent: days, vendor, limit) that the schema's generic additionalProperties object does not enumerate. It still leaves some ambiguity about which parameters are required per route beyond the vendor asterisk.

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?

Names a specific question the tool answers (which vulnerabilities to patch first for one vendor, optionally one product) and states exactly which datasets it joins (NVD CVSS, FIRST EPSS, CISA KEV). An agent could not confuse this with any listed sibling such as airports or colors.

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

Usage Guidelines4/5

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

The framing question establishes the use case, and the description gives concrete routing guidance: /answer for patch ordering, /kev-recent for recent KEV entries, and sample=true for a free 3-row preview instead of paying. It stops short of explicit when-not-to-use or prerequisites (e.g. what happens if the vendor is unknown or has no CVEs).

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