Skip to main content
Glama
msaad00

agent-bom

by msaad00
OverviewSchemaRelated ServersScoreDiscussions
Python

Blast Radius Analysis

blast_radius
Read-onlyIdempotent

Determine the spread of a CVE through your AI agents. Scans MCP configurations to list affected servers, agents, and exposed credentials.

Instructions

Look up the blast radius of a specific CVE across your AI agent setup.

    Scans local MCP configurations, finds the specified CVE, and returns
    the full attack chain: which packages are affected, which MCP servers
    use those packages, which agents connect to those servers, and what
    credentials and tools are exposed.

    Args:
        cve_id: The CVE identifier (e.g. "CVE-2024-1234" or "GHSA-xxxx").

    Returns:
        JSON with blast radius details including risk_score,
        affected_servers, affected_agents, exposed_credentials, and
        exposed_tools. Returns found=false if CVE not found.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cve_idYesCVE identifier to look up, e.g. 'CVE-2024-1234' or 'GHSA-xxxx'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, indicating no side effects. The description adds behavioral context by explaining it scans local configurations, finds the CVE, and returns an attack chain. No contradictions with annotations.

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 description is front-loaded with purpose but includes a 'Returns' section that duplicates output schema; this extra information is unnecessary given the existence of an output schema. Minor reduction for redundancy.

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 a single parameter, good annotations, and an output schema, the description covers the tool's functionality well. It explains the scanning process and return structure, though the return values are already in the schema. Overall complete for the tool's complexity.

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% for the single parameter 'cve_id', which is described concisely in both schema and description. The description adds a note about format examples but does not significantly augment the schema. Baseline 3 is appropriate.

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?

The description clearly states the tool looks up the blast radius of a specific CVE across an AI agent setup. It uses a specific verb-resource combination ('look up blast radius of a specific CVE') and distinguishes from sibling scanning tools that perform broader security analyses.

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 description implies usage when a user has a CVE identifier and wants to understand its impact. It provides context (scans local MCP configs) but does not explicitly state when to avoid this tool or mention alternatives among siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/msaad00/agent-bom'

If you have feedback or need assistance with the MCP directory API, please join our Discord server