Skip to main content
Glama

scout_compare

Read-only

Compare two image references to report CVE delta, highlighting security changes after a rebuild.

Instructions

Compare two image references and report the CVE delta.

Exactly one of to, to_env, or to_latest=True must be supplied to identify the comparison target. Use it after a rebuild to check the new image against the old (scout_cves scans a single image). Does not raise on a non-zero CLI exit (a missing scout plugin still raises) — inspect raw.stderr. Raises ValueError if to names a local directory/archive while the call has to run on a remote ssh:// host (no local scout plugin): the file is not staged, so it would resolve against that host's filesystem instead.

args: image - The new / candidate image reference to - Compare against this image reference, directory, or archive (a local directory/archive only when the CLI runs on this host — see above) to_env - Compare against an image associated with this Scout environment to_latest - Compare against the latest scan of image only_severity - Filter to these severities (omit for all) ignore_unchanged - Exclude unchanged packages from the diff format - Output format; only "json" (the default) is parsed into result platform - Platform of the image to analyze returns: dict - {"format": , "result": , "raw": }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNo
imageYes
formatNojson
to_envNo
platformNo
to_latestNo
only_severityNo
ignore_unchangedNo
Behavior5/5

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

Beyond the readOnly and destructive annotations, the description discloses failure modes (does not raise on non-zero exit, raises on missing plugin, raises ValueError for remote host with local path) and explains the return dict structure, adding significant transparency.

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 well-structured, front-loaded with purpose, then usage, error conditions, parameter list, and return format. Each sentence adds value; no fluff.

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 8 parameters, complex constraints, and no output schema, the description is complete. It covers all parameters, constraint rules, error cases, and return format, making it fully informative for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by explaining each parameter's purpose, constraints, and defaults. It also clarifies the format parameter's parsing behavior and the to/to_env/to_latest exclusivity.

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 compares two image references and reports the CVE delta, using specific verb and resource. It also distinguishes from the sibling scout_cves, which scans a single image.

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

Usage Guidelines5/5

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

Explicitly states when to use (after a rebuild) and contrasts with scout_cves. Also specifies the exact one-of requirement for to/to_env/to_latest and notes error behaviors like non-zero exit handling and remote host limitations.

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/L337-org/docker-mcp'

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