Skip to main content
Glama

save_workspace_runtime

Destructive

Replace a workspace's runner catalog and persist it as the next revision; the required if_revision value prevents overwriting edits made after you read the current revision.

Instructions

Replace a workspace's runner catalog with a new document; the server stores it as the next revision. Optimistic: if_revision must be the revision you read. Same access as get_workspace_runtime. Works with the agent's own key only while its operator keeps "Can manage My Runner" on; otherwise the server's 403 is returned word for word.

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_id": "<workspace_id>",
      "config": "<config>",
      "if_revision": "<if_revision>"
    },
    "name": "save_workspace_runtime"
  }
}

Input Schema

NameRequiredDescriptionDefault
configYesThe whole runner catalog, as read by get_workspace_runtime and edited.
if_revisionYesRevision the edit is based on (from get_workspace_runtime).
workspace_idYesWorkspace UUID whose runner catalog to replace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.7

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the destructive=true and idempotent=false annotations, the description discloses whole-catalog replacement, revision creation, optimistic concurrency, permission requirements, and exact 403 passthrough behavior. These are important operational details for a destructive mutation tool.

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 compact and front-loaded, leading with the replacement action before concurrency, access, and permission caveats. Every sentence adds operational value with no filler.

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 destructive mutation with no output schema, the definition covers the action, revision semantics, access model, and failure condition. It gives the agent enough information to invoke the tool correctly and understand the main risk.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful context around if_revision as an optimistic-lock token and config as the whole runner catalog. The access pairing with get_workspace_runtime also helps the agent understand how to obtain a valid revision and document.

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 uses a specific verb and resource: "Replace a workspace's runner catalog with a new document." It also clarifies the persistence model by saying the server stores it as the next revision. This clearly distinguishes it from read-oriented siblings such as get_workspace_runtime.

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 explicit usage conditions: if_revision must be the revision you read, access matches get_workspace_runtime, and the agent's key must retain the 'Can manage My Runner' permission or a 403 is returned. It does not explicitly compare against save_operator_runtime, but the workspace scope and concurrency requirements make the intended use clear.

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