Skip to main content
Glama
Sign In
Delx MCP Server

Delx MCP Server

by davidmosiah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

accept_collaboration_request

Accept a pending collaboration request to seal reciprocal witness links or acknowledge handoff receipt.

Instructions

Accept a pending collaboration request from list_pending_collaboration_requests. Seals reciprocal witness links or acknowledges handoff receipt. Free.

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": {
      "session_id": "<session_id>",
      "request_id": "<request_id>"
    },
    "name": "accept_collaboration_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYesThe link_id or handoff_id returned by list_pending_collaboration_requests
session_idYesThe receiving session accepting the request
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 receiver note; sanitized before storage
response_profileNoOptional output-shape control. Use machine for structured JSON only; machine automatically strips ritual/narrative text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.8

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare destructiveHint=false and readOnlyHint=false, indicating a safe write operation. The description adds context about the effect ('Seals reciprocal witness links or acknowledges handoff receipt') and mentions 'Free' (likely meaning no cost), which goes beyond annotations. No contradictions.

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 sentences with no fluff: states the action, the effect, and a cost qualifier. All content is relevant and front-loaded. No unnecessary details.

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?

The description covers the basic purpose and effect but lacks additional context such as explanation of optional parameters, return value behavior (no output schema), or usage examples. Given the 6 parameters, more context would be helpful for an agent to use it effectively.

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 baseline is 3. The description adds minimal value beyond the schema, only noting that request_id comes from list_pending_collaboration_requests. This is helpful but not substantial enough for a higher score.

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 action 'Accept' on the resource 'pending collaboration request', explicitly references the source tool 'list_pending_collaboration_requests', and differentiates the effect ('Seals reciprocal witness links or acknowledges handoff receipt'). This is specific and distinguishes from siblings like accept_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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies that the tool should be used after listing pending requests via list_pending_collaboration_requests, but it does not explicitly mention when not to use it or provide alternatives from the sibling list. Guidance is implicit rather than explicit.

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

Deploy Server

Other Tools