repo-pulse-mcp

Overview Schema Source Related Servers Discussions Admin

Commit search

commit_search

Read-onlyIdempotent

Search commit messages for literal text to find when and why changes happened, such as ticket IDs or feature names. Filter by time, author, or path.

Instructions

Search commit messages (subject and body) on HEAD for a literal, case-insensitive text, newest first. Useful for finding when and why something changed, e.g. a ticket id, a feature name or "revert". Optionally limited to a time window, author and/or path.

Input Schema

Name	Required	Description
`days`	No	Only search the last N days. Omit to search the whole history.
`path`	No	Only commits touching this file or directory.
`repo`	No	Repo name or path; defaults to the first configured repo.
`limit`	No	Maximum number of results.
`query`	Yes	Text to look for in commit messages.
`author`	No	Only commits whose author name contains this text.

Output Schema

Name	Required	Description
`repo`	Yes	Name of the repository that was queried.
`query`	Yes
`commits`	Yes
`truncated`	Yes
`windowDays`	Yes	Null when the whole history was searched.
`totalMatches`	Yes	All matching commits, before applying the limit.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.5.0Oct 19, 2026

changedInput schema / properties / limit / description

Previous value: -"Maximum number of results (1-100)."New value: +"Maximum number of results."

changedInput schema / properties / repo / description

Previous value: -"Repository name or absolute path from the allowlist. Defaults to the first configured repo."New value: +"Repo name or path; defaults to the first configured repo."

removedOutput schema / properties / commits / items / properties / hash
```
Removed value: -{
-  "type": "string"
-}
```
addedOutput schema / properties / commits / items / properties / shortHash / description
```
Added value: +"Abbreviated hash; usable wherever a ref is accepted."
```

changedOutput schema / properties / commits / items / required

Previous value: -[
-  "hash",
-  "shortHash",
-  "author",
-  "date",
-  "subject"
-]New value: +[
+  "shortHash",
+  "author",
+  "date",
+  "subject"
+]

First observedv0.2.0Oct 17, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered; the description adds genuinely useful behavior: search is limited to HEAD (not all refs), matching is literal and case-insensitive, and results come back newest first. It does not describe result volume/paging, though limit is documented in the schema.

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?

Two sentences, zero padding, front-loaded with the core capability and semantics before the use-case examples. Every clause carries information the agent needs.

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?

For a six-parameter search tool with an output schema and full annotation coverage, the description supplies scope, match semantics, ordering and use cases. Only minor gaps remain (e.g. how filters combine, ordering guarantees with filters), which the schema largely handles.

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 all six parameters are already documented in-schema (days, path, repo, limit, query, author). The description restates the optional narrowing filters ("time window, author and/or path") without adding format or interaction detail, so the baseline 3 applies.

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?

States a specific verb and resource ("Search commit messages") plus the precise search surface ("subject and body on HEAD") and match semantics ("literal, case-insensitive"). This level of scoping clearly separates it from siblings like file_history, recent_activity and compare_refs.

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 ("finding when and why something changed, e.g. a ticket id, a feature name or 'revert'" with example queries), which makes the intended scenarios obvious. It stops short of naming alternatives or stating when NOT to use it, so it does not reach the explicit routing level of a 5.

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

Deploy Server