langchain-mcp-tools 0.0.13__py3-none-any.whl → 0.0.14__py3-none-any.whl

langchain_mcp_tools/langchain_mcp_tools.py

@@ -43,9 +43,9 @@ The key aspects are:
      (based on [the mcp python-sdk impl as of Jan 14, 2025](https://github.com/modelcontextprotocol/python-sdk/tree/99727a9/src/mcp/client))
    - Initializing multiple MCP servers in parallel requires a dedicated
      `asyncio.Task` per server
-   - Necessity of keeping sessions alive for later use by different tasks
+   - Need to keep sessions alive for later use by different tasks
      after initialization
-   - Ensuring proper cleanup later in the same task that created them
+   - Need to ensure proper cleanup later in the same task that created them
 
 2. Solution Strategy:
    A key requirement for parallel initialization is that each server must be
@@ -73,7 +73,7 @@ The key aspects are:
 
 3. Task Lifecycle:
 
-   To allow the initialization task to stay alive waiting for cleanup:
+   The following illustrates how to implement the above-mentioned strategy:
    ```
    [Task starts]
      ↓

{langchain_mcp_tools-0.0.13.dist-info → langchain_mcp_tools-0.0.14.dist-info}/METADATA

@@ -1,6 +1,6 @@
 Metadata-Version: 2.2
 Name: langchain-mcp-tools
-Version: 0.0.13
+Version: 0.0.14
 Summary: Model Context Protocol (MCP) To LangChain Tools Conversion Utility
 Project-URL: Bug Tracker, https://github.com/hideya/langchain-mcp-tools-py/issues
 Project-URL: Source Code, https://github.com/hideya/langchain-mcp-tools-py
@@ -125,9 +125,9 @@ Any comments pointing out something I am missing would be greatly appreciated!
      (based on [the mcp python-sdk impl as of Jan 14, 2025](https://github.com/modelcontextprotocol/python-sdk/tree/99727a9/src/mcp/client))
    - Initializing multiple MCP servers in parallel requires a dedicated
      `asyncio.Task` per server
-   - Necessity of keeping sessions alive for later use by different tasks
+   - Need to keep sessions alive for later use by different tasks
      after initialization
-   - Ensuring proper cleanup later in the same task that created them
+   - Need to ensure proper cleanup later in the same task that created them
 
 2. Solution Strategy:
 
@@ -156,7 +156,7 @@ Any comments pointing out something I am missing would be greatly appreciated!
 
 3. Task Lifecycle:
 
-   To allow the initialization task to stay alive waiting for cleanup:
+   The following illustrates how to implement the above-mentioned strategy:
    ```
    [Task starts]
      ↓

langchain_mcp_tools-0.0.14.dist-info/RECORD

@@ -0,0 +1,8 @@
+langchain_mcp_tools/__init__.py,sha256=Xtv2VphhrWB_KlxTIofHZqtCIGtNEl0MxugnrNXTERA,94
+langchain_mcp_tools/langchain_mcp_tools.py,sha256=LptcccMFDM9t9ZYPOGvNuTBW7JFPP8Nhv3JwLr0Mits,10561
+langchain_mcp_tools/py.typed,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
+langchain_mcp_tools-0.0.14.dist-info/LICENSE,sha256=CRC91e8v116gCpnp7h49oIa6_zjhxqnHFTREeoZFJwA,1072
+langchain_mcp_tools-0.0.14.dist-info/METADATA,sha256=XNhz-pzd91ROR5Av0wjJ4qvB3dGcLST_ruBUKprJhrE,6962
+langchain_mcp_tools-0.0.14.dist-info/WHEEL,sha256=In9FTNxeP60KnTkGw7wk6mJPYd_dQSjEZmXdBdMCI-8,91
+langchain_mcp_tools-0.0.14.dist-info/top_level.txt,sha256=aR_9V2A1Yt-Bca60KmndmGLUWb2wiM5IOG-Gkaf1dxY,20
+langchain_mcp_tools-0.0.14.dist-info/RECORD,,

langchain_mcp_tools-0.0.13.dist-info/RECORD

@@ -1,8 +0,0 @@
-langchain_mcp_tools/__init__.py,sha256=Xtv2VphhrWB_KlxTIofHZqtCIGtNEl0MxugnrNXTERA,94
-langchain_mcp_tools/langchain_mcp_tools.py,sha256=5OKa6xeS54vB-mqH1BTZSB6E8Ykh5Cfu9rXqfCqESOg,10558
-langchain_mcp_tools/py.typed,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
-langchain_mcp_tools-0.0.13.dist-info/LICENSE,sha256=CRC91e8v116gCpnp7h49oIa6_zjhxqnHFTREeoZFJwA,1072
-langchain_mcp_tools-0.0.13.dist-info/METADATA,sha256=tJx9mGu94T09xAYPSCB14V1cIp7w31cM1ndNbUev1vQ,6959
-langchain_mcp_tools-0.0.13.dist-info/WHEEL,sha256=In9FTNxeP60KnTkGw7wk6mJPYd_dQSjEZmXdBdMCI-8,91
-langchain_mcp_tools-0.0.13.dist-info/top_level.txt,sha256=aR_9V2A1Yt-Bca60KmndmGLUWb2wiM5IOG-Gkaf1dxY,20
-langchain_mcp_tools-0.0.13.dist-info/RECORD,,