mcp-fabric-api

git_update_credentials

Set Git credentials for a Fabric workspace by selecting Automatic, None, or a configured connection to manage authentication for Git operations.

Instructions

Update the Git credentials configuration for the current user in a workspace

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>",
      "source": "<source>"
    },
    "name": "git_update_credentials"
  }
}

Input Schema

Name	Required	Description
`source`	Yes	Credential source type
`workspaceId`	Yes	The workspace ID
`connectionId`	No	Connection ID (required when source is ConfiguredConnection)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.8.0Sep 6, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutating but non-destructive nature is covered. The description adds useful scope ('current user in a workspace') but does not disclose whether existing credentials are overwritten or whether a prior Git connection is required.

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?

A single, focused sentence that contains no filler and states the action, resource, and scope immediately. Every word earns its place.

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?

The description is adequate for a simple update operation with fully documented parameters and safety annotations, but it leaves out behavioral context such as what 'credentials configuration' means in practice and when a connectionId is relevant. An agent could call it correctly but may not understand the full impact.

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 parameters are already documented. The description adds no additional semantics about the source enum values or the conditional connectionId requirement, so the baseline of 3 applies.

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 action ('Update') and a specific resource ('Git credentials configuration') scoped to 'the current user in a workspace'. This distinguishes it from siblings like git_get_credentials and git_connect, though it does not explicitly name alternatives.

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?

No guidance is given about when to use this tool versus alternatives such as git_connect, git_initialize_connection, or git_get_credentials. The description provides no exclusions, prerequisites, or decision criteria.

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

Deploy Server