dzstudio-mcp

Overview Schema Source Related Servers Discussions Admin

switch_session

Set a different dzStudio collaboration session as current so an agent can read scenes, modify objects, and manage locks in that session context.

Instructions

Make another session the current one.

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": "<session>"
    },
    "name": "switch_session"
  }
}

Input Schema

Name	Required	Description	Default
`session`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.3Nov 8, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not explain whether the previous session is left, whether authentication or membership is required, or what side effects occur when the current session changes.

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 a single efficient sentence with the outcome front-loaded. There is no wasted wording, though the brevity reflects under-specification rather than completeness.

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 state-changing session tool with no annotations, no output schema, and an undocumented parameter, the description is too thin. It omits the effect on the previously active session and the expected identifier format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single required parameter, so the description must compensate. It implies the parameter identifies the target session but says nothing about whether it expects a session ID, name, or other identifier format.

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 gives a clear verb-and-resource outcome: making another session the current one. It does not distinguish this from siblings such as join_session, leave_session, or session_info, so it falls short of 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?

There is no explicit when-to-use guidance, no exclusions, and no alternative named. The phrase 'another session' only weakly implies that an existing current session is being replaced.

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