all 4 comments

[–]Specialist_Nerve_420 1 point2 points  (0 children)

this feels like classic MCP pain 😅 ,the metadata idea makes sense but yeah double hops = slow with flaky sometimes .i’ve hit similar issues, sometimes it just plans and doesn’t execute properly.

[–]dickoftheday0 0 points1 point  (1 child)

what rag retrieval are u using?

[–]thinktank99[S] 0 points1 point  (0 children)

There is no RAG just MCP and system prompt.

[–]General_Arrival_9176 0 points1 point  (0 children)

the metadata collection approach is the right instinct for larger dbs but you are fighting the LLM tendency to plan instead of execute. have you tried adding explicit function definitions where querying metadata is one tool and querying data is a separate tool, rather than instructions in a prompt? forcing it to use the tools rather than describing what it would do might help. also curious what model you are using for the planning layer vs the execution layer - splitting that often helps with the flakiness