Skip to main content
Glama

studio_open_project

Opens or initializes a freeform canvas project directory, optionally imports RP/1 JSON or .rp1 source, and starts or reuses the local Studio service to return canvas context.

Instructions

打开或初始化自由画布工程目录(可选从 RP/1 JSON 或 .rp1 源码导入),启动或复用本机单端口 Studio 服务并返回画布上下文。

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": {
      "projectDir": "<projectDir>"
    },
    "name": "studio_open_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
nameNo
portNo
domainNo
projectDirYes
sourcePathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare a non-read-only, non-destructive, non-open-world operation, so the description does not need to re-state safety. It does add genuine value beyond them: a local service process is started or reused on a single port and canvas context is returned. It omits what happens on port conflicts, whether an existing project is overwritten, and whether the import is additive or replaces content.

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?

A single dense sentence that front-loads the primary action and appends the optional import and service startup as qualifiers. No filler, though the parenthetical could be split for scannability.

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?

Six parameters with zero schema descriptions and no output schema make this a parameter-heavy tool where the description carries full burden. It covers the intent but not the meaning of half the inputs or the failure modes of launching a server, so an agent would be guessing on several fields.

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 description coverage is 0% across six parameters, so the description must compensate and largely does not. It hints at projectDir (工程目录), sourcePath (RP/1 JSON or .rp1 import), and port (单端口), but leaves name, url, and the mobile/web domain enum entirely unexplained.

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?

States a concrete verb+resource pair (open or initialize a free-canvas project directory), plus the secondary effects of starting/reusing a local single-port Studio service and returning canvas context. It never names or contrasts with siblings such as create_blank_project or axure_open, so the agent cannot tell from the text alone which entry point to pick.

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?

The only usage signal is the parenthetical that import from RP/1 JSON or .rp1 source is optional. There is no statement of when this tool should be chosen over create_blank_project, axure_open, or studio_get_context, and no preconditions or exclusions.

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

Deploy Server

Other Tools