fix: Add explicit type annotations to MCP tool parameters

Fixes #393

- Add TagType annotation to write_note.tags parameter
- Replace StringOrInt type alias with inline union type in build_context.depth
- Ensures MCP protocol compatibility with clients that require explicit types

MCP clients like qwen code were skipping these tools due to missing or
non-serializable type information in parameter schemas. All MCP tool
parameters must have explicit, JSON-serializable type annotations.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Paul Hernandez <phernandez@users.noreply.github.com>

Author: github-actions[bot]

src/basic_memory/mcp/tools/build_context.py

@@ -16,8 +16,6 @@
     memory_url_path,
 )
 
-type StringOrInt = str | int
-
 
 @mcp.tool(
     description="""Build context from a memory:// URI to continue conversations naturally.
@@ -39,7 +37,7 @@
 async def build_context(
     url: MemoryUrl,
     project: Optional[str] = None,
-    depth: Optional[StringOrInt] = 1,
+    depth: str | int | None = 1,
     timeframe: Optional[TimeFrame] = "7d",
     page: int = 1,
     page_size: int = 10,

src/basic_memory/mcp/tools/write_note.py

@@ -28,7 +28,7 @@ async def write_note(
     content: str,
     folder: str,
     project: Optional[str] = None,
-    tags=None,
+    tags: TagType = None,
     entity_type: str = "note",
     context: Context | None = None,
 ) -> str: