Forgetful
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SERVER_PORT | No | HTTP server port | 8020 |
| EMBEDDING_MODEL | No | Embedding model | BAAI/bge-small-en-v1.5 |
| MAX_GRAPH_LIMIT | No | Upper bound for graph limit | 2000 |
| MEMORY_TOKEN_BUDGET | No | Max tokens for query results | 8000 |
| MEMORY_NUM_AUTO_LINK | No | Auto-link count | 3 |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| discover_forgetful_toolsA | Discover available tools, optionally filtered by category Returns enough information for LLMs to call tools directly without needing how_to_use. Args: category: Optional category filter (user, memory, project, code_artifact, document, entity, linking) ctx: FastMCP Context (automatically injected) Returns: Dictionary with: - tools_by_category: Tools grouped by category - total_count: Total number of tools - categories_available: List of available categories - filtered_by: Category filter applied (if any) All Available ToolsUser Tools - User profile and preferences
Memory Tools - Atomic knowledge storage (<400 words per memory)
Provenance Tracking (optional fields for create_memory/update_memory):
Project Tools - Organize memories by context/scope
Code Artifact Tools - Reusable code snippets and patterns
Document Tools - Long-form content (>300 words)
Entity Tools - Real-world entities (people, orgs, devices)
Workflow
|
| how_to_use_forgetful_toolB | Get detailed documentation for a specific tool Returns complete documentation including JSON schema, multiple examples, and full parameter details. Args: tool_name: Name of the tool to get documentation for ctx: FastMCP Context (automatically injected) Returns: Detailed tool documentation with JSON schema |
| execute_forgetful_toolA | Execute any registered tool dynamically. Forgetful is a semantic memory system for LLMs. Quick Start - One-Shot Examples (all required params shown)Memory Operations:
Project Organization:
Entities (people, orgs, devices):
Documents (long-form content >300 words):
Code Artifacts (reusable snippets):
Linking Best PracticesAlways link related items for discoverability:
Tool Categoriesmemory | project | entity | document | code_artifact | linking | user Use discover_forgetful_tools(category?) for full parameter details and optional params. Args: tool_name: Name of the tool to execute arguments: Dictionary of arguments to pass to the tool ctx: FastMCP Context (automatically injected) Returns: Tool execution result (format depends on the specific tool) |
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 3 tools
The three gateway tools are mostly distinct: discover_forgetful_tools lists the catalog, execute_forgetful_tool runs a tool, and how_to_use_forgetful_tool returns full parameter docs. However, discover and how_to_use overlap somewhat since both return information needed to invoke tools, forcing agents to decide between them.
All names are snake_case and consistently suffixed with the _forgetful_tool(s) qualifier. The pattern mostly follows verb_noun, though how_to_use_forgetful_tool breaks the short verb_noun rhythm used by the other two.
Only 3 exposed tools is thin on the surface, but this is a deliberate gateway/router design fronting a large (~40-tool) semantic memory catalog. It is well-scoped, though it forces extra round-trips compared to direct tool exposure.
The underlying surface covers CRUD for memories, projects, entities, documents, and code artifacts, plus linking and provenance tracking — a thorough domain model. Minor gaps exist (e.g., no direct memory hard-delete, limited cross-resource link listing), but core workflows are fully reachable via execute.