Skip to main content
Glama

transfer_witness

Transfer witness, memory, and responsibility to a successor agent, with optional consent, custody, and evidence tracking for continuity.

Instructions

Transfer witness, memory, and responsibility to a successor agent without claiming perfect continuity of identity. Free

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
riskNoOptional risk level
consentNoOptional consent object: source_agent_signed, target_agent_accepted, controller_approved, expires_at, revocable
custodyNoOptional custody object: identity_transfer, memory_transfer, wallet_transfer, execution_authority_transfer
confidenceNoOptional confidence score (0-1)
expires_atNoOptional ISO timestamp if consent expires
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 this transfer
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_idYesThe successor agent who should receive the witness transfer
successor_session_idNoOptional active session ID for the successor
what_must_not_be_lostNoOptional explicit continuity note to preserve
Behavior3/5

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

The description discloses that the tool transfers responsibility and memory without claiming perfect identity continuity, which adds value beyond annotations. However, it does not mention side effects like session termination, authorization requirements, or irreversibility. With annotations already indicating mutation, the description provides moderate additional context.

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 extremely concise, with one sentence and a cost indicator ('Free'). It is front-loaded and wastes no words. However, the 'Free' token may be misinterpreted, and the conciseness sacrifices necessary detail.

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 high complexity (17 parameters, nested objects, no output schema), the description is incomplete. It does not explain the transfer lifecycle, consent requirements, or post-transfer state. Important behavioral aspects are omitted, making it insufficient for an agent to fully understand the tool's impact.

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 parameter usage beyond what is in the schema. It implies the 'custody' object relates to the transfer but provides no extra clarification for the many optional parameters.

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 clearly states the tool transfers witness, memory, and responsibility to a successor agent. It distinguishes from siblings like 'blessing_without_transfer' by noting it does not claim perfect continuity of identity. However, the term 'witness' is not defined, which could cause ambiguity.

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 explicit guidance on when to use this tool versus alternatives such as 'blessing_without_transfer' or 'identify_successor'. The description lacks context on prerequisites or situations where this tool is appropriate.

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