Abhishek Kumar 8484e4bfaf test(mcp): guard instructions.py against tool drift ... The MCP `instructions` hint is static and baked into the client prompt, while tool names, signatures, and error codes are discovered dynamically via tools/list. The two had drifted: instructions restated stale signatures and an error-code enum that omitted schema_validation and trigger_path_conflict. - Trim instructions.py to tool names + call order; stop restating signatures and error codes the dynamic surface already carries. - Document each tool's full error_code contract in the save_workflow and create_workflow docstrings (the descriptions shipped via tools/list). - Add test_mcp_instructions_drift.py: every tool named in the guide must be registered, and every error_code a tool returns must appear in its description. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-05-20 18:44:18 +05:30
..
__init__.py	feat: refactor node spec and add mcp tools (#244)	2026-04-21 07:56:16 +05:30
catalog.py	feat: add create workflow tool in MCP	2026-04-25 17:38:38 +05:30
create_workflow.py	test(mcp): guard instructions.py against tool drift	2026-05-20 18:44:18 +05:30
docs_search.py	feat(mcp): add search_docs tool over docs corpus (closes #295) (#316)	2026-05-20 18:20:35 +05:30
get_workflow_code.py	feat: add create workflow tool in MCP	2026-04-25 17:38:38 +05:30
node_types.py	feat: add Tuner Integration to Dograh (#311)	2026-05-20 14:37:33 +05:30
save_workflow.py	test(mcp): guard instructions.py against tool drift	2026-05-20 18:44:18 +05:30
workflows.py	feat: add create workflow tool in MCP	2026-04-25 17:38:38 +05:30