adityamparikh commented on issue #85:
URL: https://github.com/apache/solr-mcp/issues/85#issuecomment-4184647644

   Hi Jeff @jzonthemtn, 
   
   Thanks for the PR https://github.com/apache/solr-mcp/pull/86. It became 
easier to understand what you're trying to accomplish. Listing a few 
considerations  - 
   
   Server scope: The primary concern of this MCP server is interacting with a 
running Solr instance. A ref guide lookup doesn't interact with the user's Solr 
deployment; it's documentation retrieval, which would be a different concern.   
                                              
   
   Context7: Solr documentation lookup is already available via 
https://context7.com/apache/solr, whose primary purpose is providing up-to-date 
library documentation to LLMs. Users can configure Context7 alongside this MCP 
server today.
   
   Approach: Parsing XML from the Solr website sitemap via a remote call that 
is not an API endpoint would be brittle. More importantly, returning URLs would 
not helpful to an LLM since it has no browser to follow them.
   
   MCP clients with web search/fetch capabilities: These LLMs can already 
navigate to solr.apache.org/guide directly and find relevant documentation on 
their own — the tool becomes a redundant middleman.  
   MCP clients without web search/fetch: For these, returning URLs is even less 
useful since there's no way to follow them. To be genuinely helpful in this 
scenario, the tool would need to fetch the matched pages and return actual 
content excerpts — but at that point we're reimplementing what Context7 already 
does.
   
   If we are seeing cases where LLM in an MCP client is not able to invoke the 
right tool correctly, perhaps we can try improving the tool description?  
   
   MCP Resource: If the goal is to give the LLM more context about specific 
Solr instance to help it use tools correctly, @McpResource with URI templates 
(e.g. solr://collections/{name}/schema) would be the right MCP primitive for 
exposing contextual data about the specific Solr instance — schema, config, 
cluster state. That's distinct from general-purpose documentation, which would 
belong in a documentation server like Context7.                                 
                            
     


-- 
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