Skip to main content
Glama
Coalesce-Software-Inc

coalesce-transform-mcp

Official

Update Git Account

update_git_account
Idempotent

Partially update a Git account's name, authentication, author info, provider, or owner.

Instructions

Update an existing Git account. Partial update — only provided fields are changed.

Args:

  • gitAccountID (string, required): The account ID

  • name (string, optional): Updated name

  • gitUsername (string, optional): Updated git username

  • gitAuthorName (string, optional): Updated author name for git commits

  • gitAuthorEmail (string, optional): Updated email for git commits

  • gitToken (string, optional): Updated personal access token

  • provider (enum, optional): 'github' | 'gitlab' | 'bitbucket' | 'azureDevOps'

  • accountOwner (string, optional): User ID of the account owner

Returns: Updated Git account object.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoUpdated name for the git account
gitTokenNoUpdated personal access token for the git provider
providerNoGit provider type
gitUsernameNoUpdated git username for authentication
accountOwnerNoUser ID of the account owner (org admins can manage other users' accounts)
gitAccountIDYesThe git account ID
gitAuthorNameNoUpdated author name for git commits
gitAuthorEmailNoUpdated email for git commits

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
nameNo
messageNo
Behavior4/5

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

Description adds 'Partial update' detail beyond annotations. Annotations already indicate non-destructive and idempotent. No contradictions; description aligns with and supplements annotations.

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?

Very concise; single sentence for behavior then bullet list of parameters. Efficient and well-organized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given rich schema and annotations, plus output schema exists, the description provides all necessary context: partial update, return type, and parameter list.

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 coverage is 100% and descriptions in schema are detailed. Tool description repeats similar info without adding significant new meaning, thus 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?

Clearly states 'Update an existing Git account' with specific verb and resource. Partial update distinction differentiates from create and delete siblings.

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?

Indicates partial update behavior, implying use when only certain fields need modification. Does not explicitly state when not to use or name alternatives, but siblings provide context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Coalesce-Software-Inc/coalesce-transform-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server