Skip to main content
Glama

get_monitor_attestation

Download a completed run's signed Ed25519 attestation—including the canonical JSON report, SHA-256 hash, and signature—so anyone can verify it at shipsealed.com/verify without an account.

Instructions

Download the signed attestation (Ed25519) for a completed run. Returns the canonical JSON report, its SHA-256 hash, and the signature. Anyone can verify it at shipsealed.com/verify without an account.

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": {
      "api_key": "<api_key>",
      "run_id": "<run_id>"
    },
    "name": "get_monitor_attestation"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYesThe run id of a completed run.
api_keyYesAirlock Monitor API key (starts with amk_).
base_urlNoBase URL of the Monitor instance (default: https://app.shipsealed.com).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses the exact return contents, the signature algorithm, and that verification is possible externally without an account. It stops short of stating failure behavior for a non-completed run or whether the attestation is stable/idempotent across repeated downloads.

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?

Three short sentences with zero filler: purpose and artifact identity are front-loaded, return contents follow, and the verification note closes. Every sentence contributes information an agent would act on.

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

Completeness4/5

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

For a 3-parameter read tool with no annotations and no output schema, the description covers purpose, returned fields, and verification path adequately. The remaining gap is error/precondition behavior when the run is not yet completed, which matters for correct invocation sequencing.

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%, so run_id, api_key (amk_ prefix), and base_url are already documented in the schema. The description adds no additional meaning about these parameters, so the baseline of 3 applies rather than any credit for added semantics.

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 ("Download the signed attestation (Ed25519)") scoped to "a completed run", and enumerates the payload (canonical JSON report, SHA-256 hash, signature). An agent can distinguish this artifact-retrieval tool from siblings like get_monitor_run, though it never names a sibling 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?

The phrase "for a completed run" implies a precondition (the run must already be finished), and the verification sentence hints at the downstream use case. But there is no explicit when-to-use vs. when-not guidance and no reference to the alternatives (get_monitor_run, get_monitor_findings) that return related data.

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