comments

Author: labkey-matthewb

api/src/org/labkey/api/mcp/AbstractAgentAction.java

@@ -13,6 +13,12 @@
 
 import static org.apache.commons.lang3.StringUtils.isNotBlank;
 
+/**
+ * "agent" it is too strong a word, but if you want to create a tools specific chat endpoint then
+ * start here.
+ * First implement getServicePrompt() to tell your "agent its mission.  You can also listen in on the
+ * conversation to help you user get the right results.
+ */
 public abstract class AbstractAgentAction<F extends PromptForm> extends ReadOnlyApiAction<F>
 {
     protected abstract String getAgentName();

api/src/org/labkey/api/mcp/McpContext.java

@@ -9,6 +9,11 @@
 import org.springframework.ai.chat.model.ToolContext;
 import java.util.Map;
 
+/**
+ *  TODO MCP tool calling supports passing along a ToolContext.  And most all
+ *  interesting tools probably need a User and Container.  This is not all hooked-up
+ *  yet.  This is an area for further investiation.
+ */
 public class McpContext implements ContainerUser
 {
     final User user;

api/src/org/labkey/api/mcp/McpService.java

@@ -19,7 +19,15 @@
 import java.util.List;
 import java.util.function.Supplier;
 
-
+/**
+ * This service lets you expose functionality over the MCP protocol (only simple http for now).  This allows
+ * external chat sessions to pull information from LabKey Server.  These methods are also made available
+ * to chat session shosted by LabKey (see AbstractAgentAction).
+ * <p></p>
+ * These calls are not security checked.  Any tools registered here must check user permissions.  Maybe that
+ * will come as we get further along.  Note that the LLM may make callbacks concerning containers other than the
+ * current container.  This is an area for investigation.
+ */
 public interface McpService extends ToolCallbackProvider
 {
     // marker interface for classes that we will "ingest" using Spring annotations