adityamparikh commented on PR #197:
URL: https://github.com/apache/solr-mcp/pull/197#issuecomment-5658284142

   Closing in favour of keeping the per-format tools and optimising each 
signature for its format.
   
   What changed my mind is a measurement, not the design. Indexing 61 shows 
through a live server took over two minutes; Solr and the server accounted for 
under a second of that. The rest was the model emitting the payload as 
tool-call arguments, and the cost differs sharply by wire shape: the same 61 
documents are ~9,500 tokens as JSON escaped inside a string, ~8,300 as a native 
JSON array, ~5,100 as CSV text. One tool with a `format` string forces every 
format through the worst shape (a string), and the catalog saving it buys (a 
few hundred tokens once per session) is two orders of magnitude smaller than a 
single call's payload.
   
   So instead, three small PRs against `main`: `index-json-documents` takes a 
typed `documents` array (no escaping, schema-validated); 
`index-markdown-documents` starts a new document at every YAML front-matter 
block so many documents are one call; the XML creator stops prefixing fields 
with the record element name. #196's guidance stays and gets one sharper 
sentence. The `index-file` idea is not coming back in any transport-specific 
form.
   
   Branch kept for reference.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to