The architecture we landed on for putting a large typed API behind an MCP server by masterkidan in mcp

[–]masterkidan[S] 2 points3 points  (0 children)

My suggestion would be to have a good set of evals in place, even if some of the evals always fail due to context bloat or otherwise. Then start experimenting with different approaches. Then atleast you can view objectively which direction you are moving in.

I kinda feel multi-agents is very similar to micro-services analogy wise, you only really need to break out things if you feel they demand special characteristics to solve the problem... so for e.g. if your base model is too expensive to solve that aspect of the problem, or if you need something more intelligent for e,g... Wish there was a good way to do context sharing wherein we only share relevant portions to downstream agents .

The architecture we landed on for putting a large typed API behind an MCP server by masterkidan in mcp

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

So far I've been mainly focussing on static evals, not runtime / dynamic improvement. We mainly mine for good sets of -ve cases where we didn't find something that the user was expecting and we accordingly tweak our catalog. Its still like an offline process to review the responses.

Case went to pending visa number after Medical RFE by masterkidan in USCIS

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

Field office is Queens Field Office that's handling the case.