Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

Rename Workspace

update_workspace
Idempotent

Rename a workspace while keeping its id intact, so existing references keep working. Preview the name check first, then confirm to apply the change for all members.

Instructions

Rename a workspace (it needs the admin or billing role). Only the name changes: the id stays, so whatever uses the id keeps working, and every member sees the new name. workspace is required and never picked for you: pass its id, or its label for the preview. name is at most 63 characters and must differ from the names of the user's other workspaces (name_taken). With confirm=false (default) it only checks the name and changes nothing; call again with the workspace id and confirm=true after the user agreed (a label is refused there). The rename applies at once, but the workspaces list can take a moment to show the new name, so keep using the id. 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

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": "<workspace>",
      "name": "<name>"
    },
    "name": "update_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
confirmNo
workspaceYes
operation_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.10.0

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses the admin/billing role prerequisite, guarantees the id is preserved so consumers keep working, warns of a propagation lag in the workspaces list, enumerates the name_taken failure and the 63-character limit, and specifies operation_id reuse/retry semantics after a timeout. Nothing here contradicts readOnlyHint=false, destructiveHint=false, or idempotentHint=true.

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 the purpose and the key invariant (id unchanged), then the parameters, then the operation_id rule. Every sentence carries information, though the trailing operation_id paragraph reads as shared boilerplate and repeats 'keep it for confirmation and all retries' twice in substance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so return values need not be explained, and the description covers roles, parameter edge cases, failure mode (name_taken), confirmation workflow, and retry safety. What remains unstated is whether the preview returns the resolved workspace id, which an agent following the 'call again with the workspace id' instruction would need.

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?

With 0% schema description coverage the description must carry the load, and it does: workspace is required and accepts id or label (label refused at confirm), name is capped at 63 chars and must be unique, confirm toggles check-only vs apply, and operation_id is reused from preview or a fresh UUID kept across retries. Defaults and the label-refusal edge case are the main value adds; minor gap is that it never says whether accepting a label at preview returns an id.

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 ('Rename a workspace') and immediately delimits scope: 'Only the name changes: the id stays, so whatever uses the id keeps working.' This distinguishes it cleanly from the sibling create_workspace/delete_workspace tools without needing their schemas.

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?

Gives explicit procedural guidance: requires admin or billing role, preview with confirm=false (default defaults clearly stated), then confirm=true with the workspace id after user agreement, and notes a label is refused at confirmation. It does not explicitly contrast with sibling tools, but the when/when-not logic within the tool is unusually complete.

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