Skip to main content
Glama

export_slsa_provenance

Generate and optionally Ed25519-sign an in-toto v1/SLSA v1.0 provenance attestation from an evidence bundle for verifiable build provenance.

Instructions

Generates and optionally Ed25519-signs an in-toto v1 / SLSA v1.0 Provenance attestation envelope from an evidence bundle.

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": {
      "bundleId": "<bundleId>"
    },
    "name": "export_slsa_provenance"
  }
}

Input Schema

NameRequiredDescriptionDefault
signNoSign the SLSA statement with Ed25519 keypair (default: true).
bundleIdYesThe unique identifier of the evidence bundle.
builderIdNoOptional SLSA builder ID URI override.
outputPathNoOptional relative path inside the workspace to write the SLSA provenance JSON.
workspacePathNoOptional workspace path hint.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It does disclose genuinely useful behavior beyond the name: the output is a standards-compliant in-toto v1 / SLSA v1.0 envelope, signing uses Ed25519, and signing is conditional. It omits, however, whether a file is written into the workspace versus returned inline, what key material or permissions signing requires, and whether the operation is repeatable or idempotent.

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?

A single dense sentence with the artifact type, the standards versions, the signing algorithm, and the input source front-loaded. No filler, no restatement of the title.

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 five-parameter tool with no output schema and no annotations, the definition covers the what but not the outcome. It never says where the generated attestation ends up when outputPath is omitted, what a successful response contains, or what the signing key requirements are, leaving real gaps for an agent that must call it correctly.

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 description coverage is 100%, so every parameter (sign, bundleId, builderId, outputPath, workspacePath) is already documented in the schema. The description only reinforces the bundleId source and the optional signing flag, adding no syntax or format detail beyond structured fields. Baseline 3 applies.

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?

The description names a concrete verb-and-resource pair: it generates (and optionally Ed25519-signs) an in-toto v1 / SLSA v1.0 provenance attestation envelope derived from an evidence bundle. That is far more specific than a generic export, and the source (evidence bundle) and output artifact (provenance envelope) are both stated. It does not, however, explicitly distinguish itself from neighboring export tools such as export_evidence_report or export_verification_proof.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no exclusions. Nothing tells an agent when provenance export is preferred over export_evidence_report, export_verification_proof, or sign_evidence_bundle, and no conditions are given for choosing the signed versus unsigned path.

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