Skip to main content
Glama
msaad00

agent-bom

by msaad00
OverviewSchemaRelated ServersScoreDiscussions
Python

Fleet Scan

fleet_scan
Read-onlyIdempotent

Scan a list of MCP server names against the security metadata registry to assess per-server risk. Returns match status, risk category, known CVEs, and verdict.

Instructions

Batch-scan a list of MCP server names against the security metadata registry.

    Designed for fleet inventory data (EDR, SIEM, CSV exports) where
    you have server names but not versions. Returns per-server risk assessment
    with registry match status, risk category, tools, credentials, known CVEs,
    and a verdict (known-high-risk, known-medium, known-low, unknown-unvetted).

    Risk levels are category-derived (filesystem=high, database=medium,
    search=low), not made-up threat scores. Every field is traceable to a source.

    Returns:
        JSON with summary (total, matched, unmatched, risk breakdown)
        and per-server details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serversYesComma-separated or newline-separated list of MCP server names to scan. E.g. '@modelcontextprotocol/server-filesystem, brave-search, glean, 50 sleep'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint. The description adds behavioral context: batch scanning, per-server risk fields (registry match status, risk category, tools, credentials, CVEs, verdict), and explains risk levels are category-derived. 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.

Conciseness5/5

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

The description is concise, well-structured with bullet points, and front-loaded with purpose. Every sentence adds value with no redundancy.

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?

Given the tool's complexity, rich annotations, and one well-described parameter, the description covers input, process, and output clearly. The output schema exists (not shown) but the description explains return format adequately.

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?

Only one parameter 'servers' with 100% schema description coverage. The description adds format details (comma-separated or newline-separated) and example input, plus explains output structure, providing meaning beyond the schema.

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 it batch-scans MCP server names against a security metadata registry, specifying input (list of server names) and output (per-server risk assessment). It distinguishes from siblings by focusing on fleet inventory data (EDR, SIEM, CSV exports) where server versions may be unknown.

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 explicitly says it's designed for fleet inventory data where you have server names but not versions. It implies appropriate use cases without stating when not to use or naming alternatives, though the sibling tool list provides context for differentiation.

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