Skip to main content
Glama
Repository Manager

Repository Manager

Setup from yaml

repository_manager_setup_from_yaml

Set up a workspace structure from a YAML file, optionally cloning repositories and running dependency-ordered installs.

Instructions

Sets up the workspace structure from a YAML file.

install=True extends clone/pull with the fresh-machine bootstrap gap this closes (CONCEPT:RM-BOOTSTRAP): after every repository is cloned or pulled, materialize the .uv-workspace-siblings/ symlinks and run uv sync for scion-sdk and every cloned project that declares a path dependency on it, dependency-ordered (scion-sdk first). See :meth:install_projects for the mechanism and its documented limits. Install failures are reported, never masked -- setup_from_yaml returns status="error" if any project failed to install, even though every repository was still cloned/pulled.

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": {
      "yaml_path": "<yaml_path>"
    },
    "name": "repository_manager_setup_from_yaml"
  }
}

Input Schema

NameRequiredDescriptionDefault
installNo
yaml_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.5.1

TDQS

A3.5/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true; the description goes well beyond them by disclosing side effects (cloned/pulled repos, materialized `.uv-workspace-siblings/` symlinks, dependency-ordered `uv sync`) and error semantics ('failures are reported, never masked', returns status="error"). It still defers the finer limits to the `install_projects` docstring rather than stating them, and says nothing about permissions or whether an existing workspace is overwritten.

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 purpose is front-loaded in one clean sentence, but the remainder is dense with internal pointers ('See :meth:`install_projects`', 'CONCEPT:RM-BOOTSTRAP') and Sphinx markup that an agent cannot resolve. Several clauses about clone/pull could be compressed without losing meaning.

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

Completeness3/5

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

This is a side-effecting setup tool with no output schema, and the description covers the install path well but omits the non-install return shape, what happens if the target workspace already exists, and what state is left behind on partial failure. Enough to call it safely, not enough to predict its full effect.

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 description coverage is 0%, so the description must carry the load: it does a good job on `install` (what it extends, ordering, failure behavior, default implied by the schema). The required `yaml_path` parameter, however, gets no explanation of expected file format, required keys, or relative-vs-absolute path handling.

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?

The opening sentence gives a specific verb and resource: 'Sets up the workspace structure from a YAML file,' which is clear enough to pick out of the sibling list. However, it never contrasts itself with near-neighbors like repository_manager_load_projects_from_yaml, rm_workspace_setup, or repository_manager_clone_projects, so differentiation is left to inference.

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?

The bulk of the text explains what `install=True` adds, which is usage-relevant, and it points at `install_projects` for the mechanism. But it never states when to choose this tool over `load_projects_from_yaml` (which also reads YAML) or `rm_workspace_setup`, and it gives no preconditions such as an existing workspace or a required YAML shape.

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