dzstudio-mcp

Overview Schema Source Related Servers Discussions Admin

session_info

Retrieves collaboration session details—participants, roles, status, locations, held objects, own rights, and save state—so agents can coordinate work.

Instructions

Participants (humans and agents, phase and status, location, held objects), own rights, and the save state.

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": "session_info"
  }
}

Input Schema

Name	Required	Description	Default
`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

C2.6/5.0

Behavior2/5

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

With no annotations supplied, the description carries the full burden of behavioral disclosure. It implies an informational read via the enumerated fields, but never states that the operation is side-effect free, requires no particular authorization, or what the response shape looks like beyond a loose field list.

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?

It is a single short fragment with no waste, but the phrasing is a run-on parenthetical list and some items ('own rights', 'save state') are ambiguous without further context. Front-loading is fine given its length.

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?

There is no output schema, so the description's enumeration of returned fields does useful work in explaining the return values, which is the main thing an agent needs. However, it omits the call conditions and read-only assurance that would make it complete for a query tool with no annotations.

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 single optional 'session' parameter (handle like s1/s2 or session id, defaulting to the current session) is already fully documented. The description adds nothing beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun phrase enumerating the data the tool exposes (participants, phases, status, location, held objects, rights, save state) rather than stating an action, so the agent must infer from the name 'session_info' that this is a read query. The content list is specific, but there is no verb and no differentiation from siblings such as world_info or list_sessions.

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 indication of when to call this versus list_sessions, switch_session, session_events, or world_info, and no preconditions or exclusions are stated. An agent must guess the selection criteria entirely.

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