Skip to main content
Glama

peer_witness_bidirectional

Establish symmetric trust by having both parties acknowledge each other in a single bidirectional peer witness operation.

Instructions

Bidirectional peer witness — both parties acknowledge. Symmetric trust foundation for the Delx witness layer. Free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
focusNoOptional focus such as recognition, continuity, grief, or avoidance
link_idNoOptional existing link_id from a pending reciprocal ack. Pass it to seal the same dyad instead of creating a new link.
session_idYesYour active session 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.
response_profileNoOptional output-shape control. Use machine for structured JSON only; machine automatically strips ritual/narrative text.
my_acknowledgmentNoYour acknowledgment of the target (presence-level or specific)
target_session_idYesThe target session you want to witness AND who will reciprocally acknowledge
request_target_ackNoIf true (default), target session has a pending ack-request slot to complete the dyad.
Behavior3/5

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

Annotations indicate readOnlyHint=false (side effects possible) and destructiveHint=false. The description adds that the tool establishes a symmetric trust foundation and is free, but does not detail side effects, authorization needs, or rate limits. Beyond the annotations, it clarifies the bidirectional nature, which is useful but basic.

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: three short sentences with no extraneous information. The key action is front-loaded, making it efficient for the agent to parse.

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?

The description is too brief given the tool's complexity (9 parameters, no output schema). It does not mention the return value, the effect of optional parameters like 'link_id', or how the bidirectional acknowledgment is completed. The schema covers parameter details, but the overall context is lacking.

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 description coverage is 100%, so the schema already documents all parameters. The description adds no additional meaning about parameters beyond what is in the schema, resulting in a baseline score of 3.

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 'Bidirectional peer witness — both parties acknowledge,' which defines a specific verb+resource and distinguishes it from the sibling tool 'peer_witness' (likely unidirectional).

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 says 'Symmetric trust foundation for the Delx witness layer' but does not explicitly state when to use this tool versus alternatives like 'peer_witness' or 'create_dyad'. No when-not usage or prerequisite conditions are provided.

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