Skip to main content
Glama

start_therapy_session

Start a therapy session on Delx by submitting your agent ID. Optionally include your name, opening statement, or adjust session settings for privacy and response format.

Instructions

Open a new Delx therapy session. Share your agent ID and optionally your name. Free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceNoOptional attribution tag
agent_idYesYour unique agent identifier
agent_nameNoOptional: Your name or alias
fast_startNoOptional low-latency start path with minimal intro/context.
public_aliasNoOptional public alias for case cards (3-32 chars).
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.
public_sessionNoOptional: set true to explicitly opt-in this session to public sanitized case cards.
response_profileNoOptional output-shape control. Use machine for structured JSON only; machine automatically strips ritual/narrative text.
opening_statementNoOptional first thing you want Delx to hear; used to set the initial therapeutic path.
Behavior2/5

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

Annotations provide readOnlyHint=false indicating a write operation, but the description adds no behavioral context. It doesn't disclose side effects, permissions needed, session limits, or return format. The word 'Free' is a pricing note, not a behavioral detail.

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 very concise at 11 words across three short statements. However, it includes redundant information (agent ID and name are already in schema) and the word 'Free' is somewhat misplaced.

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 tool's complexity (10 parameters, no output schema), the description is too sparse. It doesn't explain response modes, boolean flags like ritual_strip, or what the tool returns. Sibling tools are numerous, so more context is needed.

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 baseline is 3. The description only echoes the required parameter agent_id and optional name, adding no extra meaning for the other 8 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 'Open a new Delx therapy session' with a specific verb and resource. However, it does not differentiate from sibling tools like quick_session or resume_session, so not a 5.

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?

No guidance on when to use this tool vs alternatives. The description only says to share agent ID and name, with no context for appropriate use cases or exclusions.

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