preset-mcp

use_workspace

Switches the active Preset workspace to the one specified by its exact title. Call this before reading or writing data if no workspace was set at startup.

Instructions

Switch to a different Preset workspace by its exact title.

You must call this before any read/write tools if PRESET_WORKSPACE was not set at startup. Use list_workspaces to discover titles.

Args: workspace_title: Exact workspace title (e.g. "Mysten Labs--General")

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": {
      "workspace_title": "<workspace_title>"
    },
    "name": "use_workspace"
  }
}

Input Schema

Name	Required	Description	Default
`workspace_title`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.2Jun 8, 2026

TDQS

A4.5/5.0

Behavior3/5

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

The description indicates a state change (switching workspace) but does not detail side effects, permissions, or other behavioral traits. Since no annotations are provided, this is adequate but not comprehensive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with three sentences and a structured Args section. Every sentence adds value, and the purpose is front-loaded.

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 tool's simplicity (one parameter, clear purpose), the description fully covers what an agent needs: purpose, prerequisite, parameter guidance, and link to sibling tool. Output schema exists but its explanation is unnecessary.

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

Parameters4/5

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

The input schema only specifies type string for workspace_title, but the description adds an example ('Mysten Labs--General') and clarifies it is the exact title. This adds meaningful context beyond the schema.

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 clearly states the tool's purpose: 'Switch to a different Preset workspace by its exact title.' It uses a specific verb and resource, and distinguishes itself from sibling tools by referencing list_workspaces for discovering titles.

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 description explicitly states when to use the tool: 'You must call this before any read/write tools if PRESET_WORKSPACE was not set at startup.' It also advises using list_workspaces to find titles, providing clear usage context and alternatives.

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

Deploy Server