Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

Create Workspace

create_workspace

Create a workspace that hosts pods, storage, tasks, and servings. Preview name validation with confirm=false, then set confirm=true to provision it; poll status until running.

Instructions

Create a workspace, the place pods, storage, tasks and servings live in. An empty workspace costs nothing; what runs in it is billed as usual. name is optional (at most 63 characters) and must differ from the names of all the user's workspaces; omit it to get a generated name like my-workspace-ab12. With confirm=false (default) it only checks the name and creates nothing; call again with confirm=true after the user agreed. The workspace is set up in the background and its status stays creating until it is running: poll the workspaces tool, and create nothing in it before then. Every write requires operation_id. Reuse the ID returned by the preview, or generate a UUID before the first call. Keep it for confirmation and all retries; a new ID means a new operation. After a timeout, check operation_status and resource state before retrying.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
confirmNo
operation_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.10.0

TDQS

A4.7/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing that creation is asynchronous with a `creating` -> `running` status transition, that a preview call creates nothing, and the billing consequence of an empty workspace. The operation_id lifecycle and post-timeout recovery guidance (check operation_status and resource state) add real behavioral context, though the final paragraph is generic boilerplate that applies to any write tool.

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?

Front-loads purpose and scope before the operational detail, and nearly every sentence carries actionable meaning. The trailing operation_id/retry paragraph is longer than needed and reads as shared boilerplate, costing a little tightness.

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?

For a 3-parameter write tool with an output schema present, the definition covers everything an agent needs: naming rules, the confirm gate, async status semantics, idempotency keys and failure recovery. Return values are correctly left to the output schema.

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?

Schema description coverage is 0%, so the description carries the full burden and does so for all three parameters: `name` is optional, capped at 63 characters, must be unique across the user's workspaces, and defaults to a generated name with an example; `confirm` carries the dry-run/commit semantics; `operation_id` covers reuse of the preview ID, UUID generation and retention across retries.

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?

States a specific verb and resource ('Create a workspace') and immediately defines the resource in the platform's vocabulary ('the place pods, storage, tasks and servings live in'), which lets an agent distinguish it from update_workspace, delete_workspace and the listing 'workspaces' tool.

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?

Explicitly prescribes the two-phase flow: confirm=false only checks the name, then call again with confirm=true after user agreement. It also names the alternative action to take while the workspace is provisioning ('poll the workspaces tool') and tells the agent not to create anything inside it before status is running.

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