Skip to main content
Glama

git_info

Retrieve git repository context, working tree status, and recent changes in a single read-only operation to understand the full picture before making modifications.

Instructions

Retrieve git repository context, working tree status, or recent changes.

Consolidated tool replacing the previous get_git_context, get_git_status, and get_recent_changes tools. Use info_type to select what subset to return.

"all" returns branch, remote, recent commits, working tree status, and staged/ modified/untracked file lists in a single response. Use this when you need the full picture before making changes.

Side effects: Read-only operation; queries git repository.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax commits to return (default 100). Work summaries report ``truncated=true`` when more commits exist in the time window.
sinceNoOptional inclusive ISO timestamp for "work_summary".
untilNoOptional exclusive ISO timestamp for "work_summary".
info_typeNoWhat git information to return: - "all": branch, remote, commits, and working tree status (default) - "context": branch name, remote URL, list of recent commits - "status": working tree status with staged/modified/untracked files - "changes": recent commits from the current branch - "work_summary": date-filtered commit/file/line summary across all branchesall

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Explicitly states 'Read-only operation; queries git repository' as side effects. With no annotations, description fully covers behavioral transparency. No contradictions.

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?

Three concise paragraphs front-loaded with purpose, then details on 'all' option, then side effects. No wasted words.

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?

Complete for a read-only tool with 4 parameters (none required) and output schema. Describes info_type options, purpose, and side effects. No gaps.

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 baseline is 3. Description does not add substantial meaning beyond parameter descriptions in schema, except for mentioning consolidation context.

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?

Clear verb 'Retrieve' and resource 'git repository context, working tree status, or recent changes'. Explicitly states it's a consolidated tool replacing previous ones, distinguishing its purpose from sibling tools.

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?

States to use 'info_type' to select subset and advises using 'all' when needing full picture before changes. Provides clear context for when to use but does not explicitly mention when not to use.

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/Mustafa-Ali-Ertugrul/allbrain-mcp'

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