Skip to main content
Glama

cachly — Explain it once. Every AI knows it.

brain_from_git

Bootstrap brain lessons from git history. Parses commit messages and infers fix/feature/refactor lessons automatically. Great for onboarding an existing codebase — run once and the brain instantly knows your team's accumulated patterns. Incremental by default: only processes new commits since the last run, so repeated calls are fast. Emits progress updates to stderr during long scans.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "brain_from_git"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax commits to process (default: 100, max: 500)
sinceNoOnly commits after this date, e.g. "2024-01-01" (optional)
branchNoGit branch to parse (default: current branch / HEAD)
repo_pathNoPath to git repository (default: current directory)
incrementalNoOnly process commits since last run (default: true). Set false to reprocess all.
instance_idNoBrain instance ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose real behavioral traits: default incremental processing, only scanning new commits since the last run, and stderr progress output during long scans. However, it never says that this writes/creates lessons in the brain, whether existing lessons are overwritten or deduplicated, or what access/permissions on the repo are needed — meaningful gaps for a mutating bootstrap operation.

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

Conciseness4/5

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

Four short sentences, front-loaded with the core action before describing mechanism, incremental behavior, and progress output. Each sentence contributes something; minor tightening possible but nothing is filler.

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?

Covers purpose and incremental semantics well for a 6-parameter tool, all of which are optional. Without an output schema, the description should say what a run yields (e.g., how many lessons were inferred, what is reported on completion), and it is silent on failure modes such as an invalid repo_path or a non-git directory.

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 every parameter (limit, since, branch, repo_path, incremental, instance_id) is already documented in the schema. The description reinforces the 'incremental' default and its consequence of only processing new commits, but adds no syntax, format, or interaction detail beyond that. Baseline 3 is appropriate.

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?

States a specific verb and resource: 'Bootstrap brain lessons from git history', then clarifies the mechanism ('parses commit messages and infers fix/feature/refactor lessons'). An agent can immediately tell this ingests a git repo rather than querying the brain, which separates it from siblings like brain_search or recall_context. It does not explicitly name a sibling alternative, which keeps it from a 5.

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?

Gives concrete usage context ('Great for onboarding an existing codebase — run once') and explains repeat-call behavior ('incremental by default... repeated calls are fast'). It does not state when NOT to use it or contrast it with learn_from_attempts or team_learn, so it falls short of the explicit-alternatives bar.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.