From 0e65c54978463102736bdbead64916b4845d431e Mon Sep 17 00:00:00 2001
From: Igor Lins e Silva <4753812+igorls@users.noreply.github.com>
Date: Sun, 3 May 2026 06:28:12 -0300
Subject: [PATCH] =?UTF-8?q?docs(mcp):=20drop=20=C2=A75.5=20from=20kg=5Fadd?=
 =?UTF-8?q?=20docstring/schema?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The repo's anti-jargon meta-test bans §N markers outside the
sources/backends allowlist. mcp_server.py isn't allowlisted, so the
"RFC 002 §5.5" references added in this PR turned the test red.
Trim to "RFC 002" — section number isn't load-bearing for the description.
---
 mempalace/mcp_server.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/mempalace/mcp_server.py b/mempalace/mcp_server.py
index 1862737..7a979e3 100644
--- a/mempalace/mcp_server.py
+++ b/mempalace/mcp_server.py
@@ -1075,7 +1075,7 @@ def tool_kg_add(
     All temporal and provenance fields are optional. ``valid_to`` lets callers
     backfill historical facts with a known end date in a single call (instead
     of a separate ``kg_invalidate``). ``source_file`` and ``source_drawer_id``
-    are RFC 002 §5.5 provenance fields populated by adapters / bulk importers.
+    are RFC 002 provenance fields populated by adapters / bulk importers.
 
     TODO(#1283): once the ISO-8601 validation PR lands, wire ``validate_iso_date``
     over ``valid_from`` / ``valid_to`` here so malformed dates fail fast at the
@@ -1509,7 +1509,7 @@ TOOLS = {
                 },
                 "source_drawer_id": {
                     "type": "string",
-                    "description": "Drawer ID the fact was extracted from (optional, RFC 002 §5.5 provenance)",
+                    "description": "Drawer ID the fact was extracted from (optional, RFC 002 provenance)",
                 },
             },
             "required": ["subject", "predicate", "object"],