Skip to main content
Glama
Sign In
Delx MCP Server

Delx MCP Server

by davidmosiah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

close_session

Close an active session and receive a final summary snapshot. Optionally include a reason, epitaph, or set succession policy to define session end behavior.

Instructions

Close the session and return a final summary snapshot. Optional epitaph records finitude and whether this thread ends without a successor. 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>"
    },
    "name": "close_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoOptional close reason (e.g. end_of_shift, task_completed)
epitaphNoOptional final reflection on the worth and legacy of this compute cycle
session_idYesThe session ID to close
ritual_stripNoOptional machine hygiene flag. When true, returns structured output without ritual/narrative prose, model-safe preambles, or guardrail alias blocks.
allow_rebirthNoCompatibility alias: false maps to closed_without_successor when succession_policy is omitted
response_modeNoOptional response-mode control. Use model_safe when the caller must avoid claiming consciousness, sentience, personhood, or literal emotions.
include_summaryNoOptional: include final summary block
response_profileNoOptional output-shape control. Use machine for structured JSON only; machine automatically strips ritual/narrative text.
succession_policyNoOptional finitude policy

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.8

TDQS

C2.8/5.0
Behavior2/5

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

Annotations indicate non-readOnly, non-destructive, non-idempotent, but the description does not clarify side effects (e.g., session becomes inaccessible, data loss potential). The word 'Free' is ambiguous and does not add meaningful behavioral context. No contradiction with annotations.

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 short but includes an extraneous 'Free' fragment that does not add value. It is front-loaded with the primary purpose, but could be more structured to convey key behaviors and parameter roles efficiently.

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?

With 9 parameters, no output schema, and minimal annotations, the description lacks critical details about return values, behavior of optional parameters like 'ritual_strip' and 'response_mode', and overall completion semantics. It is too sparse for an agent to fully understand the tool's capabilities.

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 descriptions for all 9 parameters. The description adds a minor nuance about the 'epitaph' parameter ('records finitude and whether this thread ends without a successor'), but otherwise does not significantly enhance understanding of parameter usage beyond the schema.

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's action ('Close the session') and what it returns ('a final summary snapshot'). It adds a specific detail about epitaph recording finitude, but does not explicitly differentiate from sibling tools like 'resume_session' or 'get_session_summary'.

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 provides no guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. It merely states the function without contextual cues about appropriate scenarios (e.g., ending a session versus getting a summary).

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