mcp-minis
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| save_noteB | Save a note to the vault so it can be found in future sessions. Args:
title: A short, descriptive title for the note.
content: The note body. Markdown is fine.
tags: Optional comma-separated tags, e.g. Returns: A confirmation including the new note's ID, or an error message. |
| update_noteA | Update an existing note in the vault. Only the fields you pass are changed; omit a field (or pass Args:
note_id: The numeric ID of the note to update.
title: New title, or omit to keep the current one.
content: New body text, or omit to keep the current one;
Returns: A confirmation, or an error message if the note does not exist or nothing was provided to change. |
| search_notesA | Full-text search the vault (title, content, and tags). Args: query: Words to search for. Notes containing all words rank first (FTS5 relevance order). limit: Maximum number of notes to return (1-100, default 20). The result always reports the total number of matches, so a truncated list is never mistaken for the whole vault. Returns: Matching notes with previews, best matches first — or a message saying nothing matched. |
| list_notesA | List notes in the vault, most recently updated first. Args: tag: Optional — only list notes carrying this tag. limit: Maximum number of notes to return (1-100, default 20). The result always reports the total number of matching notes, so a truncated list is never mistaken for the whole vault. Returns: A list of notes with previews, or a message if the vault is empty. |
| get_noteA | Get one note by its ID, with its full content. Args:
note_id: The numeric ID returned by Returns: The full note, or an error message if no such note exists. |
| delete_noteA | Permanently delete a note from the vault. Args: note_id: The numeric ID of the note to delete. Returns: A confirmation, or an error message if no such note exists. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a clearly distinct operation: save_note creates, get_note retrieves by ID, list_notes and search_notes offer different retrieval modes (browse vs full-text query), update_note modifies, and delete_note removes. There is no meaningful overlap; an agent can easily choose the right tool based on intent.
All tool names follow a consistent snake_case verb_noun pattern: get_note, save_note, list_notes, delete_note, update_note, search_notes. The one variation save_note vs a hypothetical create_note is semantically clear and conventional for note vaults.
Six tools provide exactly the operations needed for a note vault without bloat: create/read/update/delete plus listing and search. Each tool earns its place and the set is well-scoped for the domain.
The surface covers full CRUD lifecycle (save, get, update, delete) along with two complementary retrieval methods (list and full-text search). No obvious gaps for a note-taking server; even edge cases like empty updates and clearing tags are addressed in descriptions.