Skip to main content
Glama

get_workspace_runtime

Read-onlyIdempotent

Read a workspace's runner catalog—runners, pools, bindings, and revision—to inspect runtime configuration and access for admins or authorized operators.

Instructions

Read a workspace's runner catalog (runners, pools, bindings) with its revision. Allowed when your operator is an admin of that workspace and you are connected to it. 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"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYesWorkspace UUID whose runner catalog to read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.7

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world. The description adds genuinely new context: the admin/connected precondition, the 'Can manage My Runner' dependency on the operator's settings, and the fact that the server's 403 is propagated verbatim rather than wrapped. It doesn't mention pagination or response shape, but the return contents are described.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded in the first sentence, but the second and third sentences mix two separate permission conditions (admin + connected, then the 'Can manage My Runner' toggle) without clear structure, and the quoted permission name plus 'word for word' phrasing is dense. Nothing is truly wasted, but the auth conditions could be consolidated for faster parsing.

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 one simple parameter, annotations covering safety, and no output schema, the definition covers what the agent needs: what is returned, who may call it, and how failure surfaces. The main missing piece is how it relates to the revisions sibling, which would matter for choosing correctly.

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?

One parameter with 100% schema description coverage ('Workspace UUID whose runner catalog to read'), so the baseline is 4. The description reinforces that the identifier scopes the read to that workspace's catalog, but adds no new format or constraint detail beyond the schema.

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 — 'Read a workspace's runner catalog' — and enumerates the sub-parts (runners, pools, bindings) plus the revision, which tells an agent what payload to expect. It is not explicit about how this differs from the sibling get_workspace_runtime_revisions, so it falls short of full sibling differentiation.

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 concrete eligibility conditions — operator must be an admin of that workspace and the agent must be connected to it — which effectively tells the agent when the call will succeed. It does not name or contrast an alternative tool (e.g. the revisions variant), so there is no explicit when-not-to-use guidance.

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