Skip to main content
Glama
Repository Manager

Repository Manager

List

rm_workspace_list
Read-onlyIdempotent

Lists workspaces defined in the Repository Manager to organize and configure related git projects. Use it to see available workspaces before running setup or template actions.

Instructions

List (rm_workspace). Core workspace organization and configuration.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rm_workspace_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
installNoFor 'setup': after clone/pull, materialize each project's .uv-workspace-siblings/scion-sdk symlink and run `uv sync`, dependency-ordered (scion-sdk first, since every fleet member depends on it and it is not yet published to PyPI at the required floor). Best-effort per project; a partial failure is reported (status='error' with per-project detail in 'data'), never masked as a uniform success. See CONCEPT:RM-BOOTSTRAP.
yml_pathNoPath to workspace.yml (for 'setup', 'template', 'save').
config_dictNoDictionary representation of WorkspaceConfig (for 'save').
use_defaultNoUse the pre-filled package template for 'template'.
fleet_evidence_jsonNoBounded immutable reference JSON for fleet_evidence_check.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv3.5.7
    • removedInput schema / properties / auto_start
      Removed value: -{
      -  "default": true,
      -  "description": "For 'maintain': begin at the lowest phase with repository changes instead of always 'phase', cascading to every later phase and skipping unchanged upstream phases. Default True; set False to start at 'phase'. Ignored when 'projects' or 'force' is set.",
      -  "type": "boolean"
      -}
    • removedInput schema / properties / dry_run
      Removed value: -{
      -  "default": false,
      -  "description": "Perform a dry run for 'maintain'.",
      -  "type": "boolean"
      -}
    • removedInput schema / properties / force
      Removed value: -{
      -  "default": false,
      -  "description": "For 'maintain': bump even when no code changes are detected, and override an orphan local 'next-version' tag (delete it and re-bump) — only if that tag is NOT on the remote.",
      -  "type": "boolean"
      -}
    • changedInput schema / properties / install / description
      Previous value: -"For 'setup': after clone/pull, materialize each project's .uv-workspace-siblings/agent-connector-sdk symlink and run `uv sync`, dependency-ordered (agent-connector-sdk first, since every fleet member depends on it and it is not yet published to PyPI at the required floor). Best-effort per project; a partial failure is reported (status='error' with per-project detail in 'data'), never masked as a uniform success. See CONCEPT:RM-BOOTSTRAP."New value: +"For 'setup': after clone/pull, materialize each project's .uv-workspace-siblings/scion-sdk symlink and run `uv sync`, dependency-ordered (scion-sdk first, since every fleet member depends on it and it is not yet published to PyPI at the required floor). Best-effort per project; a partial failure is reported (status='error' with per-project detail in 'data'), never masked as a uniform success. See CONCEPT:RM-BOOTSTRAP."
    • removedInput schema / properties / job_id
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "description": "Job ID to check status for 'maintain_status' action."
      -}
    • removedInput schema / properties / part
      Removed value: -{
      -  "default": "patch",
      -  "description": "Version part to bump for 'maintain' (major, minor, patch).",
      -  "type": "string"
      -}
    • removedInput schema / properties / phase
      Removed value: -{
      -  "default": 1,
      -  "description": "Starting phase number for 'maintain'.",
      -  "type": "integer"
      -}
    • removedInput schema / properties / projects
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "description": "For 'maintain': comma-separated repo names to bump ONLY those (e.g. re-bump repos a prior run skipped) instead of the whole topological set. Restricts the bulk phase to these names."
      -}
    • removedInput schema / properties / summary
      Removed value: -{
      -  "default": true,
      -  "description": "For 'maintain_status': return a COMPACT roll-up (per-phase counts + failed set + active names + remaining count) instead of the full per-repo phase dump. Keeps the response inline at 200+ repos. Set False for the full per-repo detail.",
      -  "type": "boolean"
      -}
  2. First observedv3.5.1

TDQS

C2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds nothing beyond that: no note on output shape, no explanation of why a read-only 'list' tool carries install/yml_path/config_dict parameters, and no mention of side effects like the `uv sync` work described in the schema.

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

Conciseness2/5

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

At two short fragments there is no padding, but the brevity is under-specification rather than economy: the second sentence conveys no actionable information and the first is pure tautology. It is front-loaded with nothing an agent can act on.

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

Completeness2/5

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

An output schema exists, so return values need not be explained, but for a 5-parameter, zero-required tool the description gives no indication of what the tool does, what a bare call returns, or how the mode-specific parameters apply. It is not adequate context for correct invocation.

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

Parameters2/5

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

Schema description coverage is 100%, which normally sets a baseline of 3, but here the schema parameters are framed for 'setup', 'template', 'save', and fleet_evidence_check — none of which match the tool's stated 'list' purpose — and the description does nothing to reconcile that mismatch. The description therefore leaves the agent unable to determine which parameters are meaningful for a listing call.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description restates the name and title ("List (rm_workspace)") and appends the vague tagline "Core workspace organization and configuration," which names no verb-object pair beyond "List." It never says what is listed (projects? branches? workspaces?) and does not distinguish itself from the close sibling rm_workspace_list_branches or from rm_workspace_setup/template/save, whose modes appear in its own schema.

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

Usage Guidelines2/5

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

There is no statement of when to call this tool, no prerequisites, and no named alternative. The presence of siblings like rm_workspace_list_branches and rm_workspace_get_workspace_projects makes the missing routing guidance a real gap, leaving the agent to guess from name alone.

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

Deploy Server

Other Tools