Skip to main content
Glama

studio_project_bundle

Export, verify, import, or compare self-contained project bundles with contracts, tokens, datasets, snapshots, and referenced resources using clean relative paths and compatibility diagnostics.

Instructions

导出、校验、导入或对比自包含可迁移工程包(report/export/verify/import/compare)。包含权威文档、组件契约、tokens、变量、数据集、设计决定、版本快照及引用资源/字体闭包(全部相对路径,零宿主机绝对路径泄漏),并生成兼容诊断报告。

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

Input Schema

NameRequiredDescriptionDefault
urlNo
portNo
actionNo
outDirNo
bundleDirNo
overwriteNo
projectDirNo
includeVersionsNo
targetProjectDirNo
includeThumbnailsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

B3.1/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false and openWorldHint=false; the description adds useful behavior (bundles carry authoritative docs, contracts, tokens, snapshots and font/reference closures with strictly relative paths, and a compatibility diagnostic report is produced). It omits the risk profile that matters most for a write-capable tool: what `import` and `overwrite` do to existing content in targetProjectDir, and whether partial bundles are rejected or merged.

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 is front-loaded with the action set, followed by the bundle contents and the diagnostic-report outcome; every clause carries information. It loses a point only because the long parenthetical inventory of contents reads as a list dump rather than a structured statement of what the caller must supply.

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 10-parameter, multi-mode, write-capable tool with no output schema and no parameter descriptions, the definition should at minimum map actions to required directories and describe overwrite/import consequences. It instead spends its length describing bundle payload, so an agent cannot reliably construct a correct call from the definition alone.

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?

With 10 parameters and 0% schema description coverage, the description carries the entire burden, yet it only echoes the action enum values already present in the schema. It says nothing about outDir vs bundleDir vs projectDir vs targetProjectDir, the meaning of overwrite, includeVersions, includeThumbnails, or url/port, leaving the agent to guess destination and side-effect semantics.

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 names a specific resource (self-contained portable project bundle) and enumerates five concrete modes (report/export/verify/import/compare), so an agent knows the tool's scope without opening the schema. It stops short of 5 because it never distinguishes itself from the sibling `verify` tool, which plausibly overlaps with the `verify` action here.

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?

The action list implies the situations in which each mode applies, which is enough for an agent to pick a mode. However, there is no explicit when-to-use guidance, no statement of when to prefer this tool over the sibling `verify`, and no mention of prerequisites such as which of projectDir/bundleDir/targetProjectDir each action requires.

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