Skip to main content
Glama

who_touched

Read-onlyIdempotent

Aggregate git blame results by author for a file. Displays line counts, commit counts, and primary owner. Optionally scope analysis to a specific line range.

Instructions

Read-only. Code ownership for a file via git blame, aggregated by author. Returns each author's line count, commit count, and most recent commit date, plus the primary_owner (most lines). Pass line_start/line_end to scope to one region (e.g. a single function). Errors if cwd is not a git repo or file is untracked. Cost scales with file size; instant for typical files.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoPath inside the target git repo. Defaults to the server's current working directory.
fileYesFile path relative to the repo root, e.g. `src/auth.ts`.
functionNoOptional label echoed back in the result; cosmetic only, does not change the blame range.
line_endNoOptional 1-based end line (inclusive). Must be paired with `line_start`.
line_startNoOptional 1-based start line. Must be paired with `line_end` to take effect.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileNo
authorsNo
total_linesNo
primary_ownerNoName of the author with the most lines.
Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint. Description adds cost scaling and error conditions (non-git repo, untracked file), going beyond annotations without contradiction.

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?

Concise and well-structured: front-loaded with purpose and output, then usage details. Every sentence adds information with no redundancy.

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?

Covers purpose, output, parameter usage, error conditions, and performance. Output schema exists so return values are documented separately. Complete for the tool's complexity.

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

Parameters4/5

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

Schema coverage is 100%, baseline 3. Description adds meaning: scoping with line_start/line_end, and clarifies that 'function' is cosmetic. This adds value beyond schema.

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?

The description clearly states the tool reads code ownership via git blame, aggregated by author, and lists specific outputs (line count, commit count, primary owner). This distinguishes it from siblings like 'commit_context' or 'co_change'.

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?

Provides clear guidance on when to use line_start/line_end for scoping, error conditions, and performance characteristics. Does not explicitly mention alternatives but context is strong.

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/HasanJahidul/git-insight-mcp'

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