schema: express conditional-required constraints for grok-style tool callers

tools/file_tools.py

@@ -1452,6 +1452,22 @@ def _check_file_reqs():
             },
         },
         "required": ["mode"],
+        # The handler enforces mode-conditional requirements (see _handle_patch:
+        # mode=replace needs path+old_string+new_string; mode=patch needs patch).
+        # Express that in the schema so tool-using LLMs that honor JSON Schema
+        # literally (e.g. grok-4.3) emit the required fields up-front instead
+        # of looping on python validator errors. 1Team-Engineering/hermes-agent
+        # patch: grok-tool-call-tolerance.
+        "oneOf": [
+            {
+                "properties": {"mode": {"const": "replace"}},
+                "required": ["mode", "path", "old_string", "new_string"],
+            },
+            {
+                "properties": {"mode": {"const": "patch"}},
+                "required": ["mode", "patch"],
+            },
+        ],
     },
 }
 

tools/kanban_tools.py

@@ -1066,6 +1066,15 @@ def _board_schema_prop() -> dict[str, str]:
             "board": _board_schema_prop(),
         },
         "required": [],
+        # The handler enforces "summary or result" (line ~543). Express that
+        # constraint in the schema itself so tool-using LLMs that read JSON
+        # Schema literally (e.g. grok-4.3) emit the field instead of silently
+        # omitting both and then looping on the python validator error.
+        # 1Team-Engineering/hermes-agent patch: grok-tool-call-tolerance.
+        "anyOf": [
+            {"required": ["summary"]},
+            {"required": ["result"]},
+        ],
     },
 }