Skip to main content
Glama

save_operator_runtime

Destructive

Replace an operator's runner settings document with a new version, enforcing the expected revision to reject stale edits with a conflict and return permission errors unchanged.

Instructions

Replace your operator's runner settings (My Runner) with a new document. Optimistic: if_revision must be the revision you read, a stale one is refused with a conflict. 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": {
      "config": "<config>",
      "if_revision": "<if_revision>"
    },
    "name": "save_operator_runtime"
  }
}

Input Schema

NameRequiredDescriptionDefault
configYesThe whole runner settings document, as read by get_operator_runtime and edited.
if_revisionYesRevision the edit is based on (from get_operator_runtime; 0 for the first save).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.7

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false; the description goes further by explaining that the entire document is replaced, that stale revisions are refused with a conflict, and that authorization failures surface as the server's own 403 text. That is real context beyond the annotations. It does not say whether replacing settings disturbs currently running jobs, which would be the one remaining behavior an agent might need.

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?

Three dense sentences, front-loaded with the action, then the concurrency contract, then the permission caveat. Nothing is padded, though 'the server's 403 is returned word for word' is a slightly awkward construction that could be stated as 'a 403 is passed through unchanged.'

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?

For a destructive two-parameter write with a nested document object and no output schema, the description covers overwrite semantics, concurrency, and auth failure. The gaps are minor: no statement of what a successful save returns and no note on whether the change takes effect immediately.

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 genuine meaning for if_revision by framing it as an optimistic-concurrency token whose staleness produces a conflict rather than a silent overwrite. The config parameter is described as the 'whole' document, reinforcing that partial updates are not accepted.

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?

States a specific verb and resource: 'Replace your operator's runner settings (My Runner) with a new document.' The 'operator's' qualifier implicitly separates it from save_workspace_runtime, and the parenthetical '(My Runner)' anchors it to a concrete UI concept, but no sibling is named explicitly.

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?

Establishes the prerequisite read-modify-write workflow ('if_revision must be the revision you read') and the permission precondition ('while its operator keeps "Can manage My Runner" on'). It does not spell out when to prefer this over save_workspace_runtime, but the operator/workspace split plus the read-first flow gives an agent enough to choose correctly.

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