Repository navigation
Description
Which server?
filesystem (@modelcontextprotocol/server-filesystem)
Protocol era
Both, or not era-specific
MCP client
No response
The problem
Server: @modelcontextprotocol/server-filesystem, measured on 2.0.0 and 2.2.0 (checked: 2.3.0 ships the same search_files description and the same empty result). Run with npx -y @modelcontextprotocol/server-filesystem@<version> <dir>, stdio, Node 24, macOS.
Thanks for the rewrite from #896 / #3419. We measured it, and it clearly fixes how agents search: a small model that does search now finds files reliably.
What it doesn't fix: on questions like "How many orders are there in total?", the model usually doesn't search at all. It answers on step 1, "I don't have access to any database or system that would contain order information", while the data sits one tool call away. In a controlled test the example patterns in the description decided this:
search_files description (server 2.0.0, 4 tasks x 3 runs, answers checked in code) |
Pass |
|---|---|
| 2.0.0 original | 2/12 |
| 2.2.0 / 2.3.0 text | 2/12 |
precise rules + generic examples '**/*.ext', '**/name' |
3/12 |
precise rules + concrete examples '**/*.json', '**/*invoice*' |
9/12 (reproduced in 3 separate runs) |
The only difference between the last two rows is the two example patterns. On the two affected tasks they went from 0/6 to 6/6, and with the concrete examples the model searched **/*order* and found the data.
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)
- Add one or two realistic examples next to the generic ones, e.g.
'**/*.json','**/*report*'. Small models seem to read abstract placeholders as "this is a file utility", not "the user's data is here". - Replace the bare
No matches foundwith a hint, e.g. "No matches for '' under ''. Patterns are relative to path; use '**/' to search subdirectories." In earlier runs agents repeated non-recursive patterns up to 9 times after a bare empty result.
Which MCP feature does it demonstrate? (optional)
No response
Alternatives or workarounds you have tried
- Agent-side prompt advice ("Explore with the tools before saying information is unavailable"): 3/12 vs 1/12, still mostly refusals.
- Advising "look at the folder layout first" in the description: no effect (1/12).
- Removing search_files entirely: no effect (1/12); the refusal happens before any tool is chosen.
- A larger model (gpt-oss-120b) solved 11/12 even on 2.0.0, so this mainly affects small, cheap models. One small model and synthetic data, 12 runs per row: indicative, not universal.
Already built it locally?
No server code was changed. Each description was tested by having the client show the model only a different search_files description, with the server binary unchanged and the same tasks and repeats. Verified by code-checked answers, 12 runs per variant. The exact texts are in the case study.
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.
Activity
shivamm-gupta commentedon Nov 18, 2026
Put together a patch for this (and the related #5552 for
git_log):shivamm-gupta@b3c9386b
Summary of changes
server.tsandREADME.md, added realistic glob examples ('**/*.json','**/package.json','**/*config*') to both the tool-level description and thepatternparameter schema.mcp_server_git/server.pyandREADME.md, clarifiedgit_logdescription to state results are in reverse chronological order (newest first) and clarified thatstart_timestamp/end_timestampare optional filters.src/git/tests/snapshots/list_tools.jsonsnapshot and added a patch changeset for@modelcontextprotocol/server-filesystem.Prompt used
Per repo contribution guidelines, here is the prompt that produced the change:
cliffhall commentedon Nov 18, 2026
Triage: Priority Low (total 4)
search_filesand answer without searching; the description change is a measured improvement, and agent-side prompting is a partial workaroundBoard: Servers V2 (#43), Status
Incoming, awaiting maintainer review (no milestone yet).Tanishq67m commentedon Nov 18, 2026
Thanks @shivamm-gupta for putting this together. Before it lands I measured the patch on real builds (your commit
b3c9386bvs its parente1d154ee, filesystem 2.3.0). I also need to correct the scope of this issue.Setup:
qwen3:4b-instruct(Ollama, temperature 0.7), the same 4 file-lookup tasks as in the issue, 3 repeats each (12 runs per row), every answer checked in code.search_fileson 2.3.0e1d154eeb3c9386b, as builtAlmost every failure is the same as before: the model answers "I don't have access to any database" without calling a tool.
Correction: the 3/12 → 9/12 result in this issue was measured on 2.0.0. It still holds there (7/12 in a re-run today). On 2.3.0, realistic examples alone no longer change the behavior, whether they're the patch's examples or ours.
To find what changed between 2.0.0 and 2.3.0, I ran a 2×2. Every cell uses the description from this issue:
The new parameter descriptions (e.g. "…it must resolve inside the allowed directories" on every
path) and the rewordedlist_directory/directory_tree/get_file_infodescriptions each seem to cost a little. With 12 runs per cell I can't separate them further.So my honest read: the patch is a harmless clarity improvement, but I wouldn't expect it to fix the refusals, and I don't have a measured fix for 2.3.0 yet. I'm happy to run any candidate wording through the same A/B before it's merged; it takes about 15 minutes per variant.
Suite: https://github.com/Tanishq67m/AgentGrade/blob/main/suites/pr-5553-filesystem.yaml
Reports: https://github.com/Tanishq67m/AgentGrade/tree/main/results (files
2026-11-18-pr5553-*)