Skip to main content
Glama

import_workspace_config

Destructive

Applies YAML-defined rules, statuses, and project templates to an agent's entire workspace, restoring a previously exported configuration; export first to keep a rollback.

Instructions

Import workspace configuration from YAML. Applies rules, statuses, and project templates defined in the YAML to the whole workspace of the calling agent. Run export_workspace_config first and keep its output: it is the only rollback.

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_content": "<yaml_content>"
    },
    "name": "import_workspace_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
yaml_contentYesThe complete YAML document as one string, in the format export_workspace_config returns (export, edit, import). Required and non-empty; the server rejects YAML it cannot parse.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.6
    • changedInput schema / properties / yaml_content / description
      Previous value: -"YAML configuration content as a string."New value: +"The complete YAML document as one string, in the format export_workspace_config returns (export, edit, import). Required and non-empty; the server rejects YAML it cannot parse."
  2. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false; the description adds real value on top by disclosing blast radius (the entire workspace, not per-project) and the one recovery path (a prior export). It does not say whether existing configuration is replaced or merged, nor what happens on partial failure.

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

Conciseness5/5

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

Three sentences, no filler, with the action and effect front-loaded and the safety-critical rollback note given last for emphasis. Every sentence carries operational weight.

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, non-idempotent, single-parameter tool with no output schema, the definition covers scope, input format, and recovery. The remaining gap is replace-versus-merge semantics and partial-failure behavior, which matter for a whole-workspace destructive import.

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 the round-trip contract (export, edit, import) and warns that the server rejects unparseable YAML. That meaning goes beyond the parameter's own schema text.

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

Purpose5/5

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

States a specific verb and resource (import workspace configuration from YAML) plus the exact effect: applies rules, statuses, and project templates to the calling agent's whole workspace. The pairing with the sibling export_workspace_config is named explicitly, so an agent can distinguish the two without inspecting schemas.

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 an explicit prerequisite sequence: run export_workspace_config first and retain its output as the only rollback. That is actionable when-to-use guidance. It stops short of stating when not to use it (e.g., single-project or partial-scope edits) or any permission preconditions.

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