git: git_log description doesn't say results are newest-first or that timestamp filters are optional; small models filter to an empty window
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 1/5
- Tiempo estimado
- Menos de una hora
- Aptitud para principiantes
- 88/100
- Tipo de issue
- Documentación
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- git, typescript
- Área
- devtools
Línea de trabajo
Encuentra la definición de la herramienta git_log y lee su descripción actual. Actualiza esa descripción para indicar que los resultados aparecen primero los más recientes y que start_timestamp y end_timestamp son filtros opcionales de rango de fechas, usando la redacción sugerida en el issue. La tarea está terminada cuando la descripción comunique claramente ambos puntos; el issue no indica ninguna prueba que haya que ejecutar.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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_patherror 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 defaultrepo_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.
- Lenguaje dominante
- TypeScript
- Estrellas
- 92k
- Forks
- 12k
- Merge medio
- 3 h 12 min
- PR fusionados (30 d)
- 174
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de modelcontextprotocol/servers
-
bug server-time v2
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
modelcontextprotocol/servers#5559 ·
Los mantenedores suelen responder en 1 día
-
enhancement server-filesystem v2
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
modelcontextprotocol/servers#5553 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
chore dependencies server-fetch v2
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
modelcontextprotocol/servers#5546 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
chore dependencies v2
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
modelcontextprotocol/servers#5545 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
chore server-everything v2
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
modelcontextprotocol/servers#5542 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de modelcontextprotocol/servers
Issues similares
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 95/100
marimo-team/marimo#11949 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
Monsieur-Nico/textConvert#479 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
router-for-me/Home-Management-Center#232 ·
Los mantenedores suelen responder en 1 día
-
clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster maturity:stable P3
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
openclaw/openclaw#200937 · 1 comentario · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
bug follow-up
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
Los mantenedores suelen responder en 1 día