Skip to main content
Glama

Get deploy provenance

get_deploy_provenance
Read-only

Read the organisation's deploy provenance settings (the twin of ankra org provenance get and ankra org provenance keys): the organisation's default mode and its signing keys (public keys only, with generation and status). mode is off, warn or enforce: enforce refuses a deploy unless every image has valid provenance. One application's effective mode is get_application_provenance. Read-only; needs pipelines.read. Changing a mode and rotating or revoking a key are not offered here.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_deploy_provenance"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare read-only behavior, and the description adds key context: required pipelines.read permission, public-key-only output, and enforce-mode refusal semantics. It also discloses which related mutation operations are out of scope.

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 front-loaded with the resource and scope, then adds mode semantics, the sibling alternative, permissions, and exclusions. It is dense but mostly earns its length; the CLI twin references are somewhat extraneous for an API agent.

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 compensates by describing the returned settings: default mode and public signing keys with generation and status. It also covers mode values, enforce behavior, authorization, and the application-level alternative.

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?

The tool takes no parameters, so there is no schema parameter meaning to supplement. The baseline for zero parameters is 4, and no further parameter guidance is needed.

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 and resource: reading organisation deploy provenance settings, including default mode and signing keys. It clearly distinguishes the organisation-level view from get_application_provenance for an application's effective mode.

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 directs agents to this tool for organisation-level settings and names get_application_provenance as the alternative for application-level mode. It also states that changing modes and rotating or revoking keys are not offered here, preventing misuse.

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.