mcp-fabric-api

git_update_from_git

Update a workspace to a specified Git commit, synchronizing items from the repository. Resolve conflicts by preferring workspace or remote changes to maintain the desired state.

Instructions

Update workspace from the connected Git repository (long-running)

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": {
      "workspaceId": "<workspaceId>",
      "remoteCommitHash": "<remoteCommitHash>"
    },
    "name": "git_update_from_git"
  }
}

Input Schema

Name	Required	Description
`options`	No	Update options
`workspaceId`	Yes	The workspace ID
`workspaceHead`	No	Workspace head object ID for concurrency control
`remoteCommitHash`	Yes	The remote commit hash to update to
`conflictResolution`	No	Conflict resolution settings

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.8.0Sep 6, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already indicate mutation (readOnlyHint=false) and non-destructiveness (destructiveHint=false). The description adds the useful behavioral trait that the operation is long-running, which is beyond what annotations provide. However, it does not disclose the possibility of overriding workspace items, how conflicts are resolved, or what side effects the update may have on local workspace content.

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 is a single, front-loaded sentence with no filler. It states the action, target, source, and a key behavioral trait ('long-running') in minimal words, and every part earns its place.

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?

The tool has five parameters, nested conflict-resolution settings, and is explicitly long-running, yet there is no output schema and no explanation of what the call returns or how the agent should monitor completion. The description also fails to explain how workspaceHead, allowOverrideItems, or conflictResolution affect the update, leaving important operational context missing for a complex mutation tool.

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 parameters, including workspaceHead for concurrency control, remoteCommitHash, allowOverrideItems, and conflictResolution, are already documented in the schema. The description adds no extra parameter-level meaning, so the baseline score of 3 is appropriate.

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?

The description states a specific verb ('Update'), a direct object ('workspace'), and a source ('connected Git repository'), which clearly conveys a pull-style sync. It is distinguishably different from the sibling git_commit_to_git (push direction) and workspace_update (workspace settings), even without naming them explicitly.

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 phrase 'from the connected Git repository' implies the tool is for pulling remote changes into the workspace, which gives clear context. However, it does not explicitly state when to use this tool versus git_commit_to_git, git_get_status, or other Git tools, and no prerequisites such as needing an active Git connection are mentioned.

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

Deploy Server