fix(docs): use "collections" consistently instead of "cores" (#51)

Replace references to "cores" with "collections" in CollectionService
javadoc so AI agents see consistent terminology when interacting with
MCP tool descriptions.


---------

Signed-off-by: adityamparikh <aditya.m.parikh@gmail.com>
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

Author: adityamparikh

src/main/java/org/apache/solr/mcp/server/metadata/CollectionService.java

@@ -65,8 +65,8 @@
  * <strong>Core Capabilities:</strong>
  *
  * <ul>
- * <li><strong>Collection Discovery</strong>: Lists available collections/cores
- * with automatic SolrCloud vs standalone detection
+ * <li><strong>Collection Discovery</strong>: Lists available collections with
+ * automatic SolrCloud vs standalone detection
  * <li><strong>Performance Monitoring</strong>: Comprehensive metrics collection
  * including index, query, cache, and handler statistics
  * <li><strong>Health Monitoring</strong>: Real-time health checks with
@@ -304,7 +304,7 @@ public List<String> completeCollectionForSchema() {
 	}
 
 	/**
-	 * Lists all available Solr collections or cores in the cluster.
+	 * Lists all available Solr collections in the cluster.
 	 *
 	 * <p>
 	 * This method automatically detects the Solr deployment type and uses the
@@ -313,7 +313,8 @@ public List<String> completeCollectionForSchema() {
 	 * <ul>
 	 * <li><strong>SolrCloud</strong>: Uses Collections API to list distributed
 	 * collections
-	 * <li><strong>Standalone</strong>: Uses Core Admin API to list individual cores
+	 * <li><strong>Standalone</strong>: Uses Core Admin API to list individual
+	 * collections
 	 * </ul>
 	 *
 	 * <p>
@@ -337,8 +338,8 @@ public List<String> completeCollectionForSchema() {
 	 * natural language requests like "list all collections" or "show me available
 	 * databases".
 	 *
-	 * @return a list of collection/core names, or an empty list if unable to
-	 *         retrieve them
+	 * @return a list of collection names, or an empty list if unable to retrieve
+	 *         them
 	 * @see CollectionAdminRequest.List
 	 * @see CoreAdminRequest
 	 */
@@ -366,7 +367,7 @@ public List<String> listCollections() {
 				}
 				return cores;
 			}
-		} catch (SolrServerException | IOException e) {
+		} catch (SolrServerException | IOException _) {
 			return new ArrayList<>();
 		}
 	}
@@ -609,7 +610,7 @@ public CacheStats getCacheMetrics(String collection) {
 			}
 
 			return stats;
-		} catch (SolrServerException | IOException e) {
+		} catch (SolrServerException | IOException _) {
 			return null; // Return null instead of empty object
 		}
 	}
@@ -781,7 +782,7 @@ public HandlerStats getHandlerMetrics(String collection) {
 			}
 
 			return stats;
-		} catch (SolrServerException | IOException e) {
+		} catch (SolrServerException | IOException _) {
 			return null; // Return null instead of empty object
 		}
 	}
@@ -937,7 +938,8 @@ String extractCollectionName(String collectionOrShard) {
 	 *
 	 * <p>
 	 * This dual approach ensures compatibility with both standalone Solr (which
-	 * returns core names directly) and SolrCloud (which may return shard names).
+	 * returns collection names directly) and SolrCloud (which may return shard
+	 * names).
 	 *
 	 * <p>
 	 * <strong>Error Handling:</strong>
@@ -965,10 +967,8 @@ private boolean validateCollectionExists(String collection) {
 			// Check if any of the returned collections start with the collection name (for
 			// shard
 			// names)
-			boolean shardMatch = collections.stream().anyMatch(c -> c.startsWith(collection + SHARD_SUFFIX));
-
-			return shardMatch;
-		} catch (Exception e) {
+			return collections.stream().anyMatch(c -> c.startsWith(collection + SHARD_SUFFIX));
+		} catch (Exception _) {
 			return false;
 		}
 	}