Skip to main content
Glama

Cloud Side-Scan (Azure/GCP)

cloud_side_scan
Destructive

Run agentless cloud disk side-scan to snapshot and mount read-only, record SBOM/CVE/secret metadata, then tear down. Fail-closed returns disabled or unavailable if unable to scan.

Instructions

Trigger one agentless Azure/GCP disk side-scan and read back honest state.

    Runs the same executor as ``agent-bom cloud side-scan`` and the REST
    ``POST /v1/cloud/side-scan``: snapshot the disk, mount a temp copy on an
    in-account collector read-only, record SBOM + CVE + secret *metadata* only,
    and tear every owned temporary resource down. Requires an admin operator +
    ``cloud:write`` scope. Credentials are never accepted here — the
    executor resolves read-only credentials from the provider's default chain
    (``credentialed_smoke=false``). Fail-closed and honest: OFF → ``disabled``;
    missing extra/credentials → ``unavailable``; never a clean-workload claim.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonNoHuman audit reason for triggering the side-scan.
regionNoOptional provider region hint for client construction.
locationNoAzure location / GCP zone of the temp disk (must match the collector).
providerNoCloud provider: 'azure' or 'gcp' (AWS EBS uses the CLI side-scan entrypoint).
target_idNoManaged/persistent disk resource id to scan.
tenant_idNoTenant scope for the execution and durable lifecycle record.default
account_idNoAzure subscription id / GCP project id owning the disk + collector.
collector_idNoIn-account collector VM/instance the temp disk attaches to.
operator_roleNoOperator role for this write action (audit).viewer
idempotency_keyNoRetry-safe key; the same key reuses one execution record.
operator_scopesNoComma-separated operator scopes (audit).
scan_secrets_enabledNoInclude the redacted secret scan (type + location only, never values).
collector_resource_groupNoAzure only: resource group of the collector VM.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description thoroughly discloses behavior: it snapshots, mounts read-only, records only SBOM and redacted secret metadata, tears down temp resources, resolves credentials via the default chain (no accepted credentials), requires an admin operator, and fails closed on missing extras/credentials. It also notes idempotency key reuse. This significantly exceeds the annotation info (readOnlyHint=false, destructiveHint=true) and adds concrete details about side effects and failure modes.

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

Conciseness4/5

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

The description is succinct: a one-line summary followed by a detailed but focused paragraph covering critical behavior (snapshot/teardown, metadata-only, fail-closed states, credential handling). It's organized and free of fluff, though the second paragraph is a dense run-on that could benefit from bullet points for readability.

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 13 parameters and 100% schema coverage, the description adds essential behavioral context: how the scan works (snapshot, mount, teardown), security constraints (admin role, read-only credentials, never accepts credentials), fail-closed outcomes, and metadata-only secret handling. It also clarifies idempotency via key reuseikuha, covering operational semantics beyond the 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?

While the schema already provides per-parameter descriptions (100% coverage), the description adds context for parameters like idempotency_key (reuses execution record), provider-specific details (location/resource group), and the overall auth model (admin operator). It clarifies the relationship between parameters (e.g., target disk, collector VM) without repeating schema text, adding practical meaning.

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 defines the tool's purpose: triggers an agentless Azure/GCP disk side-scan, capturing SBOM and secret metadata only. Its scope is distinctly specified (Azure/GCP, not AWS), and it differentiates from siblings by emphasizing the agentless, read-only, metadata-only nature and the fail-closed honest results.

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?

Provides context on when to use (triggering a scan, evaluating cloud disk state) and what it does (snapshot, mount, tear down). It lacks explicit 'when NOT to use' or alternatives, but the Azure/GCP scoping and read-only credential requirements are clear. A brief mention of the CLI-side-scan for AWS would be a nice contrast, but it's not critical.

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