Skip to main content
Glama

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

Stack exposure dossier — every KEV hit on your products (premium)

get_cyber_exposure_dossier
Read-only

Stack exposure dossier — every KEV hit on your products (premium). Premium: a named stack or vendor footprint against the Ni Biashara cybersecurity shelf — every ranked KEV record touching the named vendor or product, in remediation order, with the CISA deadline calendar and band counts. The patch programme, not a list. $2.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

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": {
      "stack": "<stack>"
    },
    "name": "get_cyber_exposure_dossier"
  }
}

Input Schema

NameRequiredDescriptionDefault
stackYesvendor or product name, e.g. PHP (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover read-only, open-world and non-destructive traits, but the description adds materially new behavior: the $2.5 USDC-on-Base price, that the tool call itself is free, and the exact x402 handshake (402 → PAYMENT-SIGNATURE → delivery). It stops short of describing failure, expiry or caching behavior on the returned URL.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The payment and delivery flow is front-loaded and useful, but the first sentence restates the title verbatim, 'Premium' is repeated, and marketing framing ('The patch programme, not a list') occupies space that could carry usage guidance.

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 a one-parameter, read-only tool with full schema coverage and no output schema, the critical unknown an agent faces is that the tool returns a paid x402 URL rather than the dossier itself — and that is stated plainly. Minor residual gaps are the absence of error/expiry handling and of explicit differentiation from search_cyber_kev.

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 coverage is 100% and the single parameter already carries an example ('PHP'), so the schema does most of the work. The description's 'named stack or vendor footprint' adds only marginal gloss and slightly muddies the schema's crisper 'vendor or product name'.

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 names a specific resource (every ranked KEV record touching a named vendor or product, in remediation order, with CISA deadlines and band counts) rather than restating the name. 'The patch programme, not a list' implicitly contrasts it with the narrower list-style siblings, but no sibling is named explicitly.

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: call it when you have a named stack/vendor and want the full remediation-ordered dossier rather than a raw KEV list. There is no explicit when-to-use/when-not guidance and no named alternative such as search_cyber_kev, so an agent must infer selection from phrasing alone.

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