Skip to main content
Glama

Get application provenance

get_application_provenance
Read-only

Read the deploy provenance mode an Application resolves to (off, warn or enforce) and whether it comes from the Application or the organisation. Pass images to dry-run the verification instead: the answer says what a deploy of those images would do (deploy, deploy_with_finding, refuse or not_checked) and the verdict for each image. Signing keys are never read. Read-only; needs pipelines.read.

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_provenance"
  }
}

Input Schema

NameRequiredDescriptionDefault
imagesNoImage references to verify; omitted reads the policy.
application_idYesThe Application's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say readOnlyHint=true, but the description adds real behavioral context: it requires the pipelines.read scope, it explicitly states signing keys are never read (a privacy/data-boundary disclosure), and it explains that the response shape differs by mode (mode+origin vs deploy/deploy_with_finding/refuse/not_checked plus per-image verdicts). This is substantive information beyond the annotation.

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 dense sentences, front-loaded with the primary read behavior, then the dry-run variant, then operational constraints. No filler, though 'Pass images to dry-run the verification instead' is slightly elliptical (instead of reading the policy) and requires a re-read to parse the mode switch.

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?

There is no output schema, so the description carries the return-value burden and does so by enumerating both result vocabularies. Combined with the permission requirement and the data-boundary note, an agent has everything needed to call it correctly in either mode.

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%, so the baseline would be 3, but the description adds meaning the schema lacks: it explains that supplying images switches the tool into a dry-run verification mode and changes the returned semantics, and that omitting it reads the policy. That mode-switching behavior is not inferable from the one-line schema descriptions.

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?

States a specific verb (read) and a specific resource (the deploy provenance mode an Application resolves to), and enumerates the possible values (off, warn, enforce) plus their origin (Application vs organisation). It also distinguishes the two operating modes (policy read vs image dry-run) so an agent can tell it apart from sibling reads like get_application_code_security or get_application_auto_deploy.

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?

Gives clear conditional guidance: omit images to read the resolved policy, pass images to dry-run verification and get per-image verdicts. What's missing is any exclusion relative to sibling tools (e.g. when to prefer this over a security-versions or code-security read), so the agent gets in-tool guidance but no cross-tool routing.

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.