Skip to main content
Glama

studio_project_versions

Save, list, and preview named project versions, then restore a chosen version with revision and preview checks to create an undoable transaction.

Instructions

命名保存、列出和预览工程版本;恢复需当前baseRevision、预览返回的previewHash及唯一idempotencyKey,产生可撤销新事务。保存包含设计决定、页面、组件、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_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
nameNo
portNo
actionNo
versionIdNo
projectDirNo
previewHashNo
baseRevisionNo
idempotencyKeyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, closed-world. The description adds real context beyond them: restore does not mutate in place but produces a reversible new transaction (可撤销新事务), and a save carries design decisions, pages, components, tokens, data and resource references. It does not disclose what happens on version-name collisions or how listing is paginated, keeping it below 5.

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?

Two dense clauses, front-loaded with the action inventory before the restore prerequisites and save payload. Nothing is redundant, though the semicolon-chained structure makes the restore/save split slightly harder to parse quickly.

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?

For a 9-parameter, 0%-coverage tool with no output schema, the description covers the critical preview-to-restore workflow and reversibility but leaves several connection/identity parameters and the list/preview return behavior undescribed. Adequate for the main flow, incomplete for full invocation.

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 0% across 9 parameters, so the description must compensate, and it only partially does: it explains baseRevision ('current'), previewHash (returned by preview) and idempotencyKey (unique) for the restore flow. url, port, projectDir, versionId and name remain undefined in both schema and description.

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 the resource (工程版本 / project versions) and enumerates the four concrete actions: named save, list, preview, restore. An agent can tell what the tool does at a glance. It does not distinguish this from siblings such as studio_project_bundle or studio_undo, so it stops 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 Guidelines4/5

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

It gives clear action-specific prerequisites: restore needs the current baseRevision, the previewHash returned by preview, and a unique idempotencyKey, which tells the agent the preview-then-restore sequence. It offers no when-not or comparison against sibling tools, so it is clear context rather than full routing guidance.

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