Skip to main content
Glama

Sync Workspace

sync_workspace

Scan Git diffs, new files, branch, and commits, then compare them against the Todo plan to automatically identify finished tasks.

Instructions

Scan the physical workspace (Git diff, new files, current branch, commits) and compare to the Todo plan to auto-detect finished work.

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

Input Schema

NameRequiredDescriptionDefault
pathNo.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, and it leaves the most important behavioral question unanswered: whether 'auto-detect finished work' merely reports detected completions or actually mutates the Todo plan by marking tasks done. It also says nothing about required state (an existing plan), error behavior when no plan exists, or whether the scan is read-only. The enumeration of scanned Git artifacts is useful context but does not resolve the mutation ambiguity.

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

Conciseness4/5

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

A single front-loaded sentence that packs the scan targets and the purpose into one clause with no filler. The parenthetical enumeration is dense but readable, and nothing is redundant. Slight cost: cramming four Git artifacts into the sentence makes it busier than necessary.

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 the definition still omits the preconditions that determine whether the call succeeds (existence and location of the Todo plan) and whether the operation has side effects on task state. Given the tool sits among many plan/verification siblings and has an undocumented path parameter, the description is not complete enough for confident invocation.

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?

There is one parameter, 'path', with 0% schema description coverage and a bare default of '.', and the description never mentions it. The agent is left to guess whether path is the repository root, a subdirectory to scan, or the workspace root containing the Todo plan. Since only one optional parameter is at stake and its name is fairly suggestive, this is a moderate rather than severe gap.

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 uses a specific verb ('Scan') on a specific resource ('the physical workspace') and enumerates the signals it inspects: Git diff, new files, current branch, commits. It also states the outcome ('auto-detect finished work' by comparing to the Todo plan), which makes it distinguishable from the raw git_* siblings. It stops short of naming the closest alternatives (verify_work, compare_work_to_prd), so a 4 rather than 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 Guidelines3/5

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

Usage is only implied: the agent can infer it should call this when it wants to reconcile actual repository state against planned tasks. There is no explicit 'use this when / do not use this when', no mention of prerequisites (must a Todo plan exist first?), and no routing away from verify_work or compare_work_to_prd, which plausibly overlap.

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