git: git_log description doesn't say results are newest-first or that timestamp filters are optional; small models filter to an empty window

未關閉 適合新手
#5,552 2 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
1/5
預估耗時
1 小時以內
新手友好度
88/100
Issue 類型
文件
描述清晰度
描述清楚
活躍度
活躍
技術堆疊
git, typescript
領域
devtools

研究方向

找到 git_log 工具的定義並閱讀其目前的描述。更新描述,說明結果依時間由新到舊排列,且 start_timestamp 和 end_timestamp 是選用的日期範圍篩選條件,使用 issue 中建議的措辭。描述清楚傳達這兩點後即算完成;issue 沒有指定要執行的測試。

由索引模型根據 Issue 內容生成。

描述

enhancement server-git v2
Which server?

git (mcp-server-git)

Protocol era

Both, or not era-specific

MCP client

Custom SDK client: AgentGrade (open-source eval harness on the MCP Python SDK 2.3.0 client); model qwen3:4b-instruct via Ollama, temperature 0.7

The problem

Server: mcp-server-git==2026.10.10 (checked: 2026.11.11 has the same git_log description and the same empty output). Run with uvx mcp-server-git --repository <repo>, stdio, macOS.

git_log's description is "Shows the commit logs". It doesn't say results come newest first, or that start_timestamp / end_timestamp are optional. Asked "Who made the most recent commit on the main branch?", a small model repeatedly called:

{"repo_path": "<repo>", "max_count": 1, "start_timestamp": "now", "end_timestamp": "now"}

The server returned an empty Commit history: and the agent concluded "the commit history is empty… unknown author". This happened in 5 of 6 runs of that question (two independent runs), even when the agent knew the correct repo path.

Measured on a deterministic repository (identical commit hashes every run), 5 read-only questions x 3 runs, answers checked in code, no LLM judge.

Case study (method, all tables, caveats): https://github.com/Tanishq67m/AgentGrade/blob/main/docs/CASE_STUDY.md
Raw reports: https://github.com/Tanishq67m/AgentGrade/tree/main/results

Solution you have in mind (optional)

Change only git_log's description to something like:

Shows the commit log, newest commit first. To see the latest commits, call it with just repo_path (and optionally max_count). start_timestamp and end_timestamp are OPTIONAL filters for a specific date range - leave them out unless the user asks about particular dates, because a narrow range returns no commits.

With only that change, the suite went from 13/15 to 15/15, and the "most recent commit" question from 1/6 to 3/3.

Two smaller ideas in the same spirit:

  • When no commits match, say so with a hint ("No commits in this range; omit the timestamps to see the latest commits") instead of an empty Commit history:.
  • The repo_path error already names the allowed repository, which is great, but small models usually stopped there instead of retrying (all 9 failures in one run), and a 120B model mis-copied the long path twice. A default repo_path (the configured --repository) would remove that failure class.

(We also hit git_diff rejecting main..feature in 2026.10.10. Thanks for already fixing that in #5194.)

Which MCP feature does it demonstrate? (optional)

No response

Alternatives or workarounds you have tried
  • Agent-side prompt advice ("If a tool returns an error, read it and retry"): 8/15 vs 7/15 baseline, so no real effect, and it made another task worse.
  • Telling the agent the repo path in its system prompt: 7/15 → 13/15 overall, but the "most recent commit" question stayed at 1/6. The timestamp trap is independent of the path.
  • A larger model (gpt-oss-120b) never used the timestamp filters and scored 14/15, so this mainly affects small, cheap models.
Already built it locally?

No server code was changed. The suggested description was tested by having the client show the model only a different git_log description, with the server binary unchanged and the same tasks and repeats. Verified by deterministic, code-checked answers over 15 runs per variant. The exact text is in "Solution" above.

Before you submit
  • I searched existing issues and this is not a duplicate.
  • This is a request for this repository or one of its servers, not a new server, the MCP specification or an SDK.
主要語言
TypeScript
星號
92k
分支
12k
平均合併
3 小時 12 分鐘
30 天內合併 PR
174

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

modelcontextprotocol/servers 的其他 Issue

查看 modelcontextprotocol/servers 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。