Skip to main content
Glama

Get application container security

get_application_container_security
Read-only

Read the vulnerability findings for the container images an Application publishes. A scan that failed is reported as a scan error rather than as zero findings, so do not read an empty result as a clean image without checking that the scan ran. Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "application_id": "<application_id>"
    },
    "name": "get_application_container_security"
  }
}

Input Schema

NameRequiredDescriptionDefault
componentNoOptional component name for a monorepo Application that publishes more than one image; omitted reports the Application's default component.
application_idYesThe Application's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotation already declares readOnlyHint=true, so 'Read-only' adds nothing, but the failed-scan-versus-zero-findings warning is genuine behavioral disclosure that prevents a dangerous misreading of empty output. It stops short of describing result shape, pagination, or staleness of scans.

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?

Three tight sentences, front-loaded with the purpose, then the interpretive caveat. The only waste is the trailing 'Read-only', which merely restates the readOnlyHint annotation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with no output schema, the definition covers purpose and one critical edge case, but it says nothing about what the findings response looks like (counts, severity grouping, per-image structure). An agent knows what to ask for but not what it will receive.

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%, including the component parameter's monorepo explanation, so the schema carries the parameter burden. The phrase 'container images an Application publishes' hints that multiple images may be involved but adds no detail about the component selector beyond what the schema already says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Read the vulnerability findings for the container images an Application publishes'. That is clearly distinct from code-scanning siblings like get_application_code_security or cluster-oriented ones like get_cluster_stack_security, though the description never names an alternative explicitly.

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

Usage Guidelines3/5

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

Usage is implied by the resource scoping (an Application's published container images) and there is a useful caution about interpreting empty results. However, it never tells the agent when to prefer this over the many neighbouring security tools (get_application_code_security, list_security_sbom_images, get_security_finding), so routing still requires inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.