Skip to main content
Glama
Coalesce-Software-Inc

coalesce-transform-mcp

Official

Create Git Account

create_git_account

Set up a Git account in Coalesce by providing authentication credentials, author details, and selecting a provider. Integrates version control for collaborative project management.

Instructions

Create a new Git account in Coalesce.

Args:

  • name (string, required): Account name

  • gitUsername (string, required): Git username for authentication

  • gitAuthorName (string, required): Author name for git commits

  • gitAuthorEmail (string, required): Email address for git commits

  • gitToken (string, required): Personal access token for the git provider

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

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

Returns: Created Git account with assigned ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName for the git account
gitTokenYesPersonal access token or authentication token for the git provider
providerNoGit provider type
gitUsernameYesGit username for authentication
accountOwnerNoUser ID of the account owner (org admins can manage other users' accounts)
gitAuthorNameYesAuthor name used for git commits
gitAuthorEmailYesEmail address used for git commits

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
nameNo
messageNo
Behavior3/5

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=false. The description adds that it returns the created account with an assigned ID, which is useful but does not elaborate on side effects or security considerations.

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 concise, front-loaded with the purpose, and uses a clear bulleted list for parameters. Every sentence is necessary and well-structured.

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?

The description covers the purpose, parameters, and return value. An output schema exists, but the description still mentions the return. It does not address error conditions or prerequisites, but for a create tool it is fairly complete.

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%, so the schema already describes parameters. The description restates them and lists enum values for provider, but does not add significant new meaning beyond the schema.

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 clearly states the tool creates a new Git account in Coalesce, specifying the action and resource. However, it does not differentiate from sibling tools like update_git_account or get_git_account, which slightly reduces clarity.

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 on when to use this tool versus alternatives such as update_git_account or list_git_accounts. There is no mention of when not to use it or any prerequisites.

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