mcp-server-sample
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_noteA | メモを1件保存する。打ち合わせの決定事項や、あとで思い出したいことを記録するときに使う。 |
| search_notesB | 保存済みのメモをキーワードで検索する。本文とタグの両方を対象にする。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| weekly_review | 保存済みのメモを読んで、今週のふりかえりを組み立てる。 |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| all-notes | これまでに保存したメモを JSON で返す。 |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one creates/ stores a note, the other retrieves notes via search. There is no overlap or ambiguity between writing and searching.
Both tool names follow a consistent verb_noun pattern (add_note, search_notes) using lowercase with underscores. The naming is predictable and clear.
With only 2 tools, the set feels minimal. While the tools cover basic create and read/search operations, the server's purpose (saving and retrieving notes) could reasonably include more tools (e.g., update, delete, list tags) to avoid being overly thin.
The domain is a personal note-taking system, but only add and search operations are provided. Missing critical operations like update, delete, and get all notes (without search) create significant gaps that would frustrate or block a typical agent workflow.