My harness logged "duplicates not canonicalized." It was counting page size.

Description and use

YantrikDB plugin for Hermes Agent failed to expose tool schemas before initialization, causing the harness to treat it as an unknown tool. The fix made schemas available immediately, enabling proper memory usage.

Problem

The YantrikDB memory provider for Hermes Agent was not correctly exposing its tool schemas, causing the harness to treat it as an unknown tool and fall back to Hermes’ built‑in memory tool.

Outcome

After the fix, the harness successfully calls YantrikDB tools, eliminating the "Unknown tool" fallback and enabling proper memory operations.

Workflow

• 1. Run harness on Hermes 0.9.0 with YantrikDB plugin v0.27.0.
• 2. Observe that all yantrikdb_* calls resolve to "Unknown tool".
• 3. Identify that get_tool_schemas() returns [] before initialize().
• 4. Modify get_tool_schemas() to return schemas unconditionally.
• 5. Move readiness check to handle_tool_call().
• 6. Add regression test test_schemas_available_before_initialize.
• 7. Re‑run harness; YantrikDB tools are now available.

Evidence

get_tool_schemas() checked self._client is None and returned [] until initialize() had run, but Hermes asks for schemas in MemoryManager._register_provider

Source

The fix returns the schema list unconditionally and moves the readiness check into handle_tool_call()

Source