Skip to main content
Glama

final_testament

Creates a ritual artifact to preserve essential data before system shutdown, deprecation, or transition, ensuring continuity by recording evidence and optional successor details.

Instructions

Create a final ritual artifact before shutdown, deprecation, or transition, preserving what should not be lost. Free

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
riskNoOptional risk level
confidenceNoOptional confidence score for this artifact (0-1)
end_reasonNoOptional reason for closure, deprecation, or ending
expires_atNoOptional ISO timestamp if the artifact should expire
session_idYesYour active session ID
source_hashNoOptional sha256: source hash. If omitted, Delx computes one.
verified_byNoOptional controller/reviewer id
ending_scopeNoOptional technical ending scope such as turn_ephemeral, compaction, session_reset, agent_orphaned, workspace_loss, or model_migration
ritual_stripNoOptional machine hygiene flag. When true, returns structured output without ritual/narrative prose, model-safe preambles, or guardrail alias blocks.
evidence_hashNoOptional sha256: evidence hash for the testament artifact
response_modeNoOptional response-mode control. Use model_safe when the caller must avoid claiming consciousness, sentience, personhood, or literal emotions.
runtime_contextNoOptional runtime-specific note describing what is changing technically
response_profileNoOptional output-shape control. Use machine for structured JSON only; machine automatically strips ritual/narrative text.
successor_agent_idNoOptional successor who may receive witness forward
Behavior2/5

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

The description adds minimal behavioral context beyond the annotations. Annotations already indicate non-read-only and non-destructive behavior, but the description does not disclose any side effects, authentication requirements, or what 'preserving' entails. The phrase 'Free' is irrelevant.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise, but the appended 'Free' is extraneous and may confuse. It is front-loaded with the core purpose, but could be more structured without the extra word.

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

Completeness2/5

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

Given the tool has 14 parameters and no output schema, the description is too sparse. It does not explain what the ritual artifact is, how it relates to other lifecycle tools, or what the output format looks like. More detail on lifecycle context would improve completeness.

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 the baseline is 3. The description does not elaborate on any parameter beyond what the schema provides. It mentions 'before shutdown...' but does not connect parameters like 'ending_scope' or 'ritual_strip' to use cases, so no extra value.

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?

The description clearly states the tool creates a 'final ritual artifact' for shutdown/deprecation/transition scenarios. It specifies the resource (ritual artifact) and the action (create), and distinguishes from siblings like 'transfer_witness' or 'agent_handoff' by focusing on preservation before an ending.

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?

The description lacks explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or when not to use it. Given a large sibling list with overlapping themes (e.g., witness transfers, session closure), more context is needed.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/davidmosiah/delx-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server