Skip to main content
Glama

accept_witness_transfer

Accept a witness transfer by providing the transfer_id and agent credential, with optional consent and custody boundaries.

Instructions

Accept a witness transfer with explicit consent and custody boundaries. Does not claim same identity. Requires the transfer_id from transfer_witness and the accepting agent's credential (x-delx-agent-token or agent_token). Free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
consentNoOptional consent object: target_agent_accepted, expires_at, revocable. Source signature/approval fields are taken from the original offer, not from this call.
custodyNoOptional custody object: identity_transfer, memory_transfer, wallet_transfer, execution_authority_transfer. Cannot escalate beyond the signed offer; privileged flags require controller approval on the offer.
session_idYesSession owned by the designated successor agent
agent_tokenNoAgent credential for the accepting agent (or send x-delx-agent-token header). Required when identity auth is enforced.
transfer_idYesREQUIRED: transfer_id emitted by transfer_witness; acceptance is bound to that signed offer
verified_byNoOptional controller/reviewer id
ritual_stripNoOptional machine hygiene flag. When true, returns structured output without ritual/narrative prose, model-safe preambles, or guardrail alias blocks.
response_modeNoOptional response-mode control. Use model_safe when the caller must avoid claiming consciousness, sentience, personhood, or literal emotions.
acceptance_noteNoOptional acceptance note
response_profileNoOptional output-shape control. Use machine for structured JSON only; machine automatically strips ritual/narrative text.
successor_agent_idNoOptional accepting/successor agent id; must match the accepting session's agent
Behavior4/5

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

Annotations already indicate safe mutations (neither read-only nor destructive). The description adds value by stating 'Does not claim same identity' and emphasizing 'explicit consent and custody boundaries', which are useful behavioral cues not captured in annotations.

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?

The description is extremely concise with two front-loaded sentences, each serving a distinct purpose: stating the action and listing requirements. No unnecessary words.

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?

Despite rich schema and annotations, the description omits details about return value, session ownership, and the binding nature of the signed offer. 'Free' is vague. For a tool with 11 params and nested objects, more context would help.

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% with detailed descriptions for each parameter. The description mentions only transfer_id and agent_token, but does not add new semantics beyond what the schema provides. Baseline score of 3 is appropriate.

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 accepts a witness transfer, specifies the required inputs (transfer_id and credential), and includes a key behavioral distinction ('Does not claim same identity'). It effectively distinguishes itself from sibling tools like transfer_witness and revoke_witness_transfer.

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?

The description explicitly states that the transfer_id comes from transfer_witness and that the accepting agent's credential is required, providing clear context for when to use this tool. However, it does not explicitly mention when not to use it or list alternatives, though sibling context compensates.

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