DIANA-MCP

diana_start

Connects to a live DianaIE session, launching DianaIE with the bridge when none is running; optionally opens a DIANA project or attaches only to an existing session.

Instructions

Connect to a live DianaIE session, launching DianaIE with the bridge if none is running.

Args: project_path: absolute path of a DIANA project (.dpf) to open. Refused if another project is open, because opening a project discards unsaved changes in the current one. working_dir: working directory for a newly launched DianaIE (default: the diana-mcp work folder). attach_only: only attach to a running bridge; never launch DianaIE. timeout_seconds: how long to wait for a newly launched DianaIE to come up.

Input Schema

Name	Required	Description	Default
`attach_only`	No
`working_dir`	No
`project_path`	No
`timeout_seconds`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.10.0Nov 4, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Since no annotations exist, the description provides vital behavioral context that goes beyond parameter definitions, specifically detailing the refusal to operate under certain project-state conditions. This prevents incorrect invocation by the agent.

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 slightly dense due to the immediate inclusion of argument details, but it is logically structured and avoids unnecessary jargon or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of starting system-level software (DianaIE/bridge), the definition is highly complete. It details environmental requirements and operational limits necessary for the agent to use this tool safely and effectively.

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

Parameters5/5

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

As the schema coverage is zero, the description must clarify all fields. It successfully explains required formats (absolute path, .dpf) and operational semantics (what the timeout waits for).

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

Purpose5/5

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

The description provides a clear and specific function: connecting to or launching a DianaIE session and bridge. It immediately sets the scope of the operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The tool specifies critical 'when-not' conditions, such as refusing to open a project if one is currently active, which prevents accidental data loss. It also clearly distinguishes between 'launch' and 'attach_only' modes.

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

Deploy Server