Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

filesystem, memory: descriptions don't say how to choose between list_directory / list_directory_with_sizes and delete_entities / delete_relations

オープン 初心者向け
  • 何か問題がありますか？
#5,071 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
2/5
見積もり時間
1〜3時間
初心者へのやさしさ
75/100
issue の種類
ドキュメント
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
typescript
領域
documentation

調査の方向性

src/filesystem と src/memory から始め、名前が挙げられている4つのツールの定義を読み、実装されている動作を確認します。名前とスキーマは変更せず、説明だけを更新し、それぞれについて、いつ使用するか、代わりにどの兄弟ツールを選ぶべきかが分かるようにします。説明がツールを正確に区別し、コードが実装していない動作を主張していなければ完了です。

索引モデルが issue の本文から書いたものです。

説明

Which server?

More than one server (filesystem and memory)

Protocol era

Both, or not era-specific

MCP client

Any. The issue is in the tool descriptions that every client shows the model.

The problem

Two pairs of tools have descriptions so alike that a model can't tell which one to call.

filesystem (2026.8.31): list_directory and list_directory_with_sizes

The descriptions are the same sentence for sentence. They differ only by ", including sizes" and "essential" vs "useful":

list_directory: Get a detailed listing of all files and directories in a specified path. Results clearly distinguish between files and directories with [FILE] and [DIR] prefixes. This tool is essential for understanding directory structure and finding specific files within a directory. Only works within allowed directories.

list_directory_with_sizes: Get a detailed listing of all files and directories in a specified path, including sizes. Results clearly distinguish between files and directories with [FILE] and [DIR] prefixes. This tool is useful for understanding directory structure and finding specific files within a directory. Only works within allowed directories.

Neither says when to pick it over the other, that list_directory_with_sizes can sort by size, or that it ends with totals.

memory (2026.8.31): delete_entities and delete_relations

delete_entities: Delete multiple entities and their associated relations from the knowledge graph

delete_relations: Delete multiple relations from the knowledge graph

Both are destructive. Asked to remove a link between two entities, a model that picks delete_entities deletes the entities themselves, with all their observations. Neither description says which one to use for that.

Solution you have in mind (optional)

Say in each description when to use the tool and when to use its sibling instead. Suggested text, written only from what the code does (I checked list_directory_with_sizes's sort and summary in dist/index.js):

  • list_directory: List the files and directories directly inside a path, each marked [FILE] or [DIR]. Use it to see what a directory contains; when you also need each entry's size or want entries sorted by size, use list_directory_with_sizes instead, and for a recursive view use directory_tree. Returns one line per entry. Only works within allowed directories.
  • list_directory_with_sizes: List the files and directories directly inside a path with each file's size, marked [FILE] or [DIR], sorted by name or by size (sortBy). Use it when sizes matter, such as finding the largest files; for names only, use list_directory, which returns less text. Returns one line per entry, followed by the totals. Only works within allowed directories.
  • delete_entities: Delete whole entities from the knowledge graph, together with every relation that points to or from them and all their observations. Use it only to remove an entity entirely; to remove a link between two entities and keep both, use delete_relations, and to remove facts from an entity, use delete_observations. Cannot be undone.
  • delete_relations: Delete specific relations (from, to, relationType) from the knowledge graph and keep the entities they connect. Use it to remove a link between two entities; to remove an entity itself, use delete_entities. Cannot be undone.
Which MCP feature does it demonstrate? (optional)

Tool descriptions, and how clients use them to choose a tool. As reference servers, these are what many people copy when writing their own.

Alternatives or workarounds you have tried

None on the server side. A client can add its own instructions, but every client would have to do it.

Already built it locally?

No code. The prompt I'd use: "In src/filesystem and src/memory, rewrite the descriptions of list_directory, list_directory_with_sizes, delete_entities and delete_relations so each says when to use it and names the sibling tool to use instead, using only behavior the code implements; keep tool names and schemas unchanged."

For context: I found these pairs with Forecall, a static linter for MCP tool descriptions that I maintain. It flags tool pairs whose descriptions overlap heavily. With the text above, its scores go from 38 and 48 to 65 and 70 for the two filesystem tools, and from 51 and 39 to 61 and 61 for the two memory tools. The scores are only a guide; the point is the missing "use X instead".

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
スター
91k
フォーク
11.8k
平均マージ
6時間 33分
マージ済み PR（30日）
79

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

modelcontextprotocol/servers のほかの issue

modelcontextprotocol/servers の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。