Skip to main content
Glama

Ingest External Scanner Report

ingest_external_scan
Destructive

Parse Trivy, Grype, or Syft JSON scan output and optionally push findings to the control plane, resolving absent findings when specified.

Instructions

Ingest Trivy, Grype, or Syft JSON scan output and optionally push findings to the control plane.

    This tool mutates the control plane when ``parse_only`` is false: it bulk-ingests
    findings and, with ``reconcile_absent``, resolves open findings absent from the batch.
    That write path is gated as a destructive action requiring the ``findings:write`` scope.
    ``parse_only`` requests parse locally only and stay a read.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceNoSource label stored on ingested findings.external_scan
scan_jsonYesJSON string from Trivy, Grype, or Syft scan output
parse_onlyNoWhen true, parse locally only. When false, bulk-ingest to the control plane when AGENT_BOM_API_URL and credentials are configured.
reconcile_absentNoWhen pushing, mark findings absent from this batch as resolved.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description discloses that the tool mutates the control plane when parse_only is false, which is beyond the annotations. It also notes the write path requires findings:write scope. This adds valuable context about behavioral traits.

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 very concise with two sentences that front-load the main action. Every sentence adds value without 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?

With 4 parameters fully described, annotations, an output schema (indicated), and moderate complexity, the description covers all necessary behavioral nuances. It doesn't need to explain return values due to output schema.

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% but the description adds meaning by explaining the write path gating and parse_only behavior. It goes beyond the schema by connecting parameters to real-world effects.

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 ingests Trivy, Grype, or Syft JSON scan output and optionally pushes findings to the control plane. It uses specific verb and resource, distinguishing it from sibling scanning tools.

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 explains when to use the tool (for external scanner reports) and the difference between parse_only true/false. It mentions the destructive action requires findings:write scope. While it doesn't explicitly state when not to use, the context is clear.

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