COD-529: Update instructions to use names

Author: sciapan

src/codealive_mcp_server.py

@@ -54,9 +54,9 @@
     - Remember that context from previous messages is maintained in the same conversation
 
     Flexible data source usage:
-    - You can use a workspace ID as a single data source to search or chat across all its repositories at once
-    - Alternatively, you can use specific repository IDs for more targeted searches
-    - For complex queries, you can combine multiple repository IDs from different workspaces
+    - You can use a workspace name as a single data source to search or chat across all its repositories at once
+    - Alternatively, you can use specific repository names for more targeted searches
+    - For complex queries, you can combine multiple repository names from different workspaces
     - Choose between workspace-level or repository-level access based on the scope of the query
 
     Repository integration:
@@ -65,7 +65,7 @@
       you can suggest using CodeAlive's search and chat to understand the codebase
     - Data sources include repository URLs to help match with local git repositories
     - Workspaces include a list of repository IDs, allowing you to understand their composition
-    - You can use repository IDs from workspaces to search or chat about specific repositories within a workspace
+    - When searching or chatting, always use repository names from workspaces to target specific repositories
 
     When analyzing search results:
     - Pay attention to file paths to understand the project structure

src/tests/test_parameter_normalization.py

@@ -50,14 +50,14 @@ def test_mixed_array_with_dicts(self):
         assert result == ["repo1", "repo2", "repo3", "workspace1"]
 
     def test_dict_without_id(self):
-        """Test that dicts without 'id' field are skipped."""
+        """Test that dicts without 'id' field use 'name' field if present."""
         input_data = [
             "repo1",
-            {"name": "some-repo", "type": "repository"},  # No 'id' field
+            {"name": "some-repo", "type": "repository"},  # No 'id' field, but has 'name'
             "repo2"
         ]
         result = normalize_data_source_names(input_data)
-        assert result == ["repo1", "repo2"]
+        assert result == ["repo1", "some-repo", "repo2"]
 
     def test_empty_strings_preserved(self):
         """Test that empty strings in arrays are preserved (might be intentional)."""

src/tools/chat.py

@@ -33,14 +33,14 @@ async def codebase_consultant(
 
     Args:
         question: What you want to know about the codebase
-                 Example: "How does the authentication system work?"
+                  Example: "How does the authentication system work?"
 
         data_sources: Repository or workspace names to analyze. These names are
                       resolved to IDs on the server side.
                       Example: ["enterprise-platform", "workspace:payments-team"]
 
         conversation_id: Continue a previous consultation session
-                        Example: "conv_6789f123a456b789c123d456"
+                         Example: "conv_6789f123a456b789c123d456"
 
     Returns:
         Expert analysis and explanation addressing your question.

src/tools/datasources.py

@@ -19,12 +19,12 @@ async def get_data_sources(ctx: Context, alive_only: bool = True) -> str:
 
     Args:
         alive_only: If True (default), returns only data sources in "Alive" state ready for use with chat.
-                   If False, returns all data sources regardless of processing state.
+                    If False, returns all data sources regardless of processing state.
 
     Returns:
         A formatted list of available data sources with the following information for each:
-        - id: Unique identifier for the data source, used in other API calls
-        - name: Human-readable name of the repository or workspace
+        - id: Unique identifier for the data source
+        - name: Human-readable name of the repository or workspace, used in other API calls
         - description: Summary of the codebase contents to guide search and chat usage
         - type: The type of data source ("Repository" or "Workspace")
         - url: URL of the repository (for Repository type only)