Skip to main content
Glama

Release: seal a software release

release_seal

Seal a software release: its file fingerprints, source commit and SBOM fingerprint, anchored on chain. Customers check any download with release_check. A sealed release cannot be changed. Requires the organization API key.

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": {
      "product": "<product>",
      "version": "<version>",
      "files": "<files>",
      "actor": "<actor>"
    },
    "name": "release_seal"
  }
}

Input Schema

NameRequiredDescriptionDefault
actorYesWho is doing this (person or agent)
filesYesRelease files, each {"name": "app-1.4.2.zip", "sha256": "<64 hex>"}
commitNoSource commit the release was built from
productYes
versionYese.g. 1.4.2
sbom_sha256NoFingerprint of the software bill of materials, if you have one

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Beyond the annotations it adds three useful facts: the anchor is on chain (external, open-world), the resulting release becomes immutable ("A sealed release cannot be changed"), and an organization API key is needed. However, with idempotentHint=false declared, it does not say what happens if the same product/version is sealed twice, nor whether the on-chain anchor exposes data publicly. Useful but incomplete for a non-idempotent write.

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 short sentences, front-loaded with the action and its payload, then routing, then the constraint. No filler; the only mild inefficiency is that the auth requirement trails at the end instead of sitting with the other invocation constraints.

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 6-parameter, 4-required mutation tool with no output schema, the description covers purpose, immutability, auth and the verification counterpart. It leaves a real gap: it never indicates what a successful seal returns (seal id, on-chain transaction reference), which the agent likely needs to persist for later release_check calls.

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 83%, so the schema already documents the parameters well; baseline is 3. The description reinforces which inputs matter most by naming file fingerprints, source commit and SBOM fingerprint, but adds no format or syntax guidance and never mentions actor, product or version, which are the required identifying fields.

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 ("Seal a software release") and enumerates exactly what gets sealed: file fingerprints, source commit, SBOM fingerprint, anchored on chain. It also names the sibling it is not (release_check) so an agent can separate the seal path from the verify path without opening either schema.

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?

Makes the consumption side clear by pointing to release_check for verifying downloads, and states the precondition "Requires the organization API key." It never explicitly says when not to use it — e.g. whether re-sealing an already-sealed product/version is a no-op or an error — but the context is clear enough to act on.

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.

Resources