Flint Note
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_note_typeC | Create a new note type with description, agent instructions, and metadata schema |
| create_noteC | Create one or more notes of the specified type(s) |
| get_noteC | Retrieve a specific note by identifier |
| get_notesC | Retrieve multiple notes by their identifiers |
| update_noteC | Update one or more existing notes |
| search_notesB | Search notes by content and/or type. Empty queries return all notes sorted by last updated. |
| search_notes_advancedC | Advanced search with structured filters for metadata, dates, and content |
| search_notes_sqlA | Direct SQL search against notes database for maximum flexibility. Only SELECT queries allowed. |
| list_note_typesA | List all available note types with their purposes and agent instructions |
| update_note_typeC | Update one or more fields of an existing note type |
| get_note_type_infoB | Get comprehensive information about a note type including instructions and description |
| list_vaultsB | List all configured vaults with their status and information |
| create_vaultB | Create a new vault and add it to the vault registry |
| switch_vaultC | Switch to a different vault |
| remove_vaultB | Remove a vault from the registry (does not delete files) |
| get_current_vaultB | Get information about the currently active vault |
| update_vaultC | Update vault information (name or description) |
| get_note_infoB | Get detailed information about a note including filename for link creation |
| list_notes_by_typeC | List all notes of a specific type with filename information |
| delete_noteC | Delete an existing note permanently |
| delete_note_typeC | Delete a note type and optionally handle existing notes |
| bulk_delete_notesC | Delete multiple notes matching criteria |
| rename_noteA | Rename a note by updating its title field (display name). The filename and ID remain unchanged to preserve links. Automatically updates wikilinks in other notes that reference the old title. |
| get_note_linksB | Get all links for a specific note (incoming, outgoing internal, and external) |
| get_backlinksC | Get all notes that link to the specified note |
| find_broken_linksA | Find all broken wikilinks (links to non-existent notes) |
| search_by_linksC | Search for notes based on their link relationships |
| migrate_linksC | Scan all existing notes and populate the link tables (one-time migration) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Available note types | List of all available note types with their descriptions |
| Recently modified notes | List of recently modified notes |
| Workspace statistics | Statistics about the current workspace |
| Individual note | Access individual notes by type and filename (e.g., flint-note://note/general/my-note) |
| Individual note in specific vault | Access individual notes by vault, type and filename |
| Notes by type | List all notes of a specific type (e.g., flint-note://notes/general) |
| Notes by type in specific vault | List all notes of a specific type in a specific vault |
| Notes by tag | List all notes with a specific tag (e.g., flint-note://notes/tagged/important) |
| Incoming links to note | List all notes that link to a specific note |
TDQS
Scored across 28 tools
Most tools have distinct purposes, but there is some overlap between search_notes, search_notes_advanced, and search_notes_sql, which could cause confusion about which to use for different search scenarios. The descriptions help clarify, but the boundaries are not perfectly clear.
Tool names follow a consistent verb_noun pattern throughout, with clear and predictable naming (e.g., create_note, delete_note, get_note, update_note). There are no deviations in style or convention, making it easy to understand the action and target.
With 28 tools, the count feels heavy for a note-taking domain, bordering on excessive. While the tools cover many aspects, it may overwhelm agents and could likely be consolidated without losing functionality.
The tool set provides comprehensive coverage for note management, including CRUD operations for notes, note types, and vaults, as well as advanced features like linking, search, and migration. There are no obvious gaps, and agents can handle full lifecycles without dead ends.