repo-pulse-mcp

Overview Schema Source Related Servers Discussions Admin

Recent activity

recent_activity

Read-onlyIdempotent

List commits on HEAD from the last N days, newest first. Optionally filter by author, repository, or file path to review code changes.

Instructions

List commits on HEAD from the last N days, newest first. Optionally filter by author (case-sensitive substring of the author name) and/or a repository-relative path.

Input Schema

Name	Required	Description
`days`	No	Time window in days.
`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.
`author`	No	Only commits whose author name contains this text.

Output Schema

Name	Required	Description
`repo`	Yes	Name of the repository that was queried.
`commits`	Yes
`truncated`	Yes
`windowDays`	Yes
`totalCommits`	Yes	All matching commits in the window, before applying the limit.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.5.0Oct 19, 2026

changedInput schema / properties / days / description

Previous value: -"Size of the time window in days."New value: +"Time window in days."

changedInput schema / properties / limit / description

Previous value: -"Maximum number of results (1-200)."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/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds behavioral detail beyond them: results are ordered newest first, the author match is a case-sensitive substring, and scope is limited to HEAD. It stops short of noting pagination or truncation behavior against the limit.

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 filler, and the core scope (HEAD, last N days, newest first) is front-loaded before the optional filters. Every clause carries information an agent needs.

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?

With an output schema present, return values need not be described, and all five parameters are documented in the schema at full coverage. The description supplies the operational context (window, ordering, filter semantics, scope) needed to invoke the tool correctly, so nothing material is missing.

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%, so the baseline is 3, but the description genuinely adds meaning: it specifies the author filter is a case-sensitive substring and that the path filter is repository-relative, neither of which the schema states. It does not restate defaults or bounds already in the schema.

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?

The description names a specific verb and resource ('List commits on HEAD from the last N days'), states ordering ('newest first'), and scopes the operation to a recency window plus optional author/path filters. It distinguishes itself functionally from broader siblings like commit_search by pinning the window to HEAD and N days, though it never names an alternative tool explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: an agent can infer 'use this for recent activity in a time window' from the description, but there is no explicit when-to-use/when-not guidance and no reference to the sibling commit_search, which is the obvious overlap. Adequate but leaves routing to inference.

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

Deploy Server