dzstudio-mcp

Overview Schema Source Related Servers Discussions Admin

leave_session

Leaves a dzStudio collaboration session after changes reach the server, waiting up to 10 seconds; use confirm to exit even when changes remain unsent.

Instructions

Leave a session once every change has reached the server (waits up to 10 s). With confirm, leave even if changes are still unsent.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "leave_session"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	No
`session`	No	Session handle (s1, s2 …) or session id; default: the current session

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.3Nov 8, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations, the description carries the full burden and does disclose the meaningful 10-second flush wait and the confirm override for unsent changes. It omits the consequences of confirm (are unsent changes discarded?), the failure behavior on timeout, and whether session state is preserved.

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?

Two short sentences, front-loaded with the action and the blocking condition, with zero filler. Structure is efficient and easy 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?

For a session-termination operation with no annotations and no output schema, important behavior is missing: what happens to unsent changes when confirm is used, whether a timeout produces an error, and what the tool returns on success. Adequate but with clear gaps.

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 50%: session is documented in the schema while confirm has no schema description. The description compensates by defining confirm's semantics ('leave even if changes are still unsent'). Baseline 3 with added meaning over the schema for the undocumented parameter.

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?

Specific verb+resource: 'Leave a session'. It also states the operational condition (waits up to 10s for changes to reach the server) and the confirm override. It is distinguishable from siblings like switch_session or release, though it doesn't name alternatives explicitly.

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?

Usage is implied: leave at the end of work, once changes have been sent, with confirm as the escape hatch. There is no explicit statement of when-not-to-use or comparison to switch_session/release, and no mention of what to do if the 10s wait times out.

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