Skip to main content
Glama

git_tools

Manage tasks with git-inspired commands: view commit history, list branches, compare task versions, generate graphs, merge tasks, and assign tasks to branches.

Instructions

[HINT: Git tools. action=commits|branches|tasks|diff|graph|merge|set_branch. Unified git-inspired tools.]

Unified git-inspired task management tools.

Actions:

  • action="commits": Get commit history (task_id or branch required)

  • action="branches": List all branches with statistics

  • action="tasks": Get all tasks in a branch

  • action="diff": Compare task versions

  • action="graph": Generate commit graph visualization

  • action="merge": Merge tasks from one branch to another

  • action="set_branch": Assign task to a branch

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNocommits
task_idNo
branchNo
limitNo
commit1No
commit2No
time1No
time2No
formatNotext
output_pathNo
max_commitsNo
source_branchNo
target_branchNo
conflict_strategyNonewer
authorNosystem
dry_runNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided, so the description must cover behavioral traits. It does not disclose side effects (e.g., data modification in merge/set_branch), state changes, or authorization needs. Only action names are listed.

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

Conciseness3/5

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

The description is relatively concise but repeats 'Unified git-inspired' and includes a potentially confusing HINT line. The action list is structured but lacks explanatory context.

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?

Given the tool's complexity (16 params, multiple actions, no schema descriptions), the description is insufficient. It does not explain how actions differ, what parameters are required for each, or expected outcomes. An output schema exists but is not referenced.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, yet the description adds little meaning to the 16 parameters. It only mentions some parameters briefly in action descriptions (e.g., task_id, branch for commits). Most parameters like limit, format, commit1, commit2, conflict_strategy are unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it is a 'unified git-inspired task management tool' with actions like commits, branches, tasks, etc. The purpose is somewhat clear but broad, as it bundles multiple operations. It does not distinguish itself from sibling tools, which include many task-related tools.

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 on when to use this tool versus alternatives. The description lists actions but does not explain scenarios for each, leaving the agent without context for selection.

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/davidl71/project-management-automation'

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