Skip to main content
Glama

get_workspace_runtime_revisions

Read-onlyIdempotent

Lists a workspace runner catalog's stored revisions, newest first, for history review and rollback. Returns the server's 403 verbatim when the agent lacks My Runner management access.

Instructions

List stored revisions of a workspace's runner catalog, newest first. 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>"
    },
    "name": "get_workspace_runtime_revisions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many revisions to return (default 50, max 200).
workspace_idYesWorkspace UUID whose catalog history to read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.7

TDQS

A3.9/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing the ordering of results, the key-scope restriction (agent's own key only), the operator-controlled "Can manage My Runner" prerequisite, and the exact 403 passthrough behavior. This is precisely the auth and failure context an agent needs before invoking.

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 tight sentences with the purpose front-loaded and the permission caveat following. Minor awkwardness in "the server's 403 is returned word for word" but nothing is wasted or padded.

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?

With no output schema, the description could say more about what a revision record contains (fields, IDs, timestamps), but it fully covers purpose, ordering, access requirements, and error semantics for a two-parameter read tool. Adequate for correct invocation.

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

Parameters3/5

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

Schema coverage is 100% and already documents both workspace_id and limit (default 50, max 200). The description adds no parameter-level meaning beyond "newest first" output ordering, so the baseline of 3 applies.

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 ("List stored revisions of a workspace's runner catalog") plus the ordering guarantee ("newest first"), which separates it from get_workspace_runtime's current-state read. It never explicitly names a sibling as the alternative, so the differentiation is implicit rather than spelled out.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Same access as get_workspace_runtime" ties this tool's context to a known sibling and the permission condition tells the agent when a call will succeed versus 403. However, there is no explicit when-to-use versus get_operator_runtime_history or guidance on choosing this over reading the live catalog.

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