Skip to main content
Glama

sync_workspace_rules

Generates AGENTS.md, .cursorrules, or CLAUDE.md from stored MindGate memories, conventions, and session handoffs. Writes are atomic, existing files are backed up, and hand-written files are protected unless forced.

Instructions

Generate a structured Markdown rules file (AGENTS.md, .cursorrules, or CLAUDE.md) from stored MindGate memories, conventions, preferences, and latest session handoff. Writes are atomic; existing files are backed up to .bak- and hand-written files are never overwritten unless force=true.

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": "sync_workspace_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoAllow overwriting an existing target file that MindGate did not generate (e.g. a hand-written AGENTS.md). A timestamped .bak backup is always created before overwriting. Default false.
workspaceNoProject workspace identifier.
project_dirNoOptional absolute path to the project directory where the rules file should be written. If omitted, returns the generated Markdown without writing to disk.
target_fileNoTarget filename to write inside project_dir (default: 'AGENTS.md').
include_globalNoWhether to include global developer preferences and memories (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.7/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full behavioral burden and does so well: it discloses atomic writes, timestamped backups, and the safeguard against overwriting hand-written files unless force=true. This gives an agent clear safety expectations for a file-writing operation.

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?

The description uses two efficient sentences: the first states the generation purpose and inputs, the second covers write safety behavior. It is front-loaded, has no redundant wording, and is appropriately sized for the tool's complexity.

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?

Given the absence of annotations and output schema, the description covers the essential behavior for a write operation, including atomicity, backups, and overwrite protection. It is nearly complete, though it could state when to choose this tool or what prerequisites apply before generating a rules file.

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 100%, so all five parameters are already documented in the input schema. The description reinforces the force behavior and names some target files, but adds no meaningful semantic detail beyond what the schema provides, making 3 the correct baseline.

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 description states a specific verb and resource: generating a structured Markdown rules file from stored MindGate memories, conventions, preferences, and session handoff. It clearly distinguishes the output type and source, but does not explicitly name or compare against any sibling tool, so it falls short of the full sibling-differentiation bar for a 5.

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?

The description does not say when to use this tool versus alternatives such as export_memory_snapshot or recall_context, nor does it state when not to use it. The intended use is implied by the purpose, but no explicit contextual guidance or prerequisite checks are provided.

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