deepset-mcp 0.0.3rc1__py3-none-any.whl → 0.0.4rc1__py3-none-any.whl

deepset_mcp-0.0.4rc1.dist-info/RECORD

@@ -0,0 +1,70 @@
+deepset_mcp/__init__.py,sha256=Ol1ZNMYGXYJfJke5HJyFUjyKbkeCZqXxwLeKheMWuSI,305
+deepset_mcp/config.py,sha256=EEq7ytCAcL6mkOTse4ZHG__oq1PImx93XBe3lKCHCzU,1853
+deepset_mcp/initialize_embedding_model.py,sha256=5Zcccrw3ItHpt0rGgM-3WdqV-QQaiv79nxBHhDSwNwA,411
+deepset_mcp/main.py,sha256=CLVzJRzgl5UGtvhPz62bBG7wSlc-B-T_hNB3lAoX324,6735
+deepset_mcp/store.py,sha256=14t4wokfUCvGXoXEcl4vEweXWgfvaR_uu9omtUxYwmM,227
+deepset_mcp/tool_factory.py,sha256=5M0g_FXzl4qBFTQHc9h5hGcuKtjSB-WuhLiLFwmTxZ0,19893
+deepset_mcp/api/README.md,sha256=h3xj8G2x1f5Z5EA6fBtBfNeVtXNwYnr291yPMmr2fQo,15576
+deepset_mcp/api/__init__.py,sha256=-32egOu1IHdVvJKcEEcbfVu4hqX1QGM8wePwThoMGBE,111
+deepset_mcp/api/client.py,sha256=Lmf5skULQSiYZ-S81gbFUGfaC6f_E104fxQd4ENA4x4,9927
+deepset_mcp/api/exceptions.py,sha256=QvkVYZteB07VjJpB2UX4lWgRK8KnS2AkeftI-MxYcvE,2545
+deepset_mcp/api/protocols.py,sha256=4GIrP-hCvgPhkOWSbCuQlty8XKg-ThupWm21Ws-2HB0,4149
+deepset_mcp/api/shared_models.py,sha256=dxQ384fNWiUP6DoFm50gsPxVorRjpwvrfISA4cUrgwM,522
+deepset_mcp/api/transport.py,sha256=pFmBHISni7uxLNoj0kFNHNvgxwuf2GQp0vmzIK4RaYI,10379
+deepset_mcp/api/custom_components/__init__.py,sha256=-32egOu1IHdVvJKcEEcbfVu4hqX1QGM8wePwThoMGBE,111
+deepset_mcp/api/custom_components/models.py,sha256=gjiKt8xn3dHHczmKAr28FSi23X1ZmN6WhXscqkX66QI,721
+deepset_mcp/api/custom_components/protocols.py,sha256=72rm0Z9DHSfQoe4vPllFGf-FdlVR7tZ5cb4hORmFooQ,737
+deepset_mcp/api/custom_components/resource.py,sha256=yfvi8pzg06ykPPemi5Jz6Jj56jXVBqdnLkFZVhyvOyc,2080
+deepset_mcp/api/haystack_service/__init__.py,sha256=-32egOu1IHdVvJKcEEcbfVu4hqX1QGM8wePwThoMGBE,111
+deepset_mcp/api/haystack_service/protocols.py,sha256=oLlTaRRezeNFHh6D8pBYcvmokjifFJlrqwfJO16Yufg,558
+deepset_mcp/api/haystack_service/resource.py,sha256=xVgXUhbkXPQg5HWd3QIbilBv87CKNrn82E4MrLLB2HM,2077
+deepset_mcp/api/indexes/__init__.py,sha256=-32egOu1IHdVvJKcEEcbfVu4hqX1QGM8wePwThoMGBE,111
+deepset_mcp/api/indexes/models.py,sha256=H0imXNrkY7f6kb3ZTmCZopMztyiK5ZfQ4TLLY94VIjA,2116
+deepset_mcp/api/indexes/protocols.py,sha256=pN-hOoVG_L_1LvPjrMIHaD3Xpt-SxtiIrN7nKWnUOY0,1932
+deepset_mcp/api/indexes/resource.py,sha256=8VXLNW9_oWoWkGLVpuOlJf4ra1wQ8DCIL_14pdCyWe4,5411
+deepset_mcp/api/integrations/__init__.py,sha256=Zg4Tahtk0ma_Xv_k8WLx98vD37s79rCFQ_ktXGnqCzw,155
+deepset_mcp/api/integrations/models.py,sha256=sdNBmBe8Njp3QY1ATM-8F6jNwCKstUuZhKxEXfaAPy4,1263
+deepset_mcp/api/integrations/protocols.py,sha256=PBQvuAKYwYua02Xr5uewUzrla9gtGhjTVRUc-RqKQeE,904
+deepset_mcp/api/integrations/resource.py,sha256=r6m3xrU2RhZWAYP6r6Sfq4EtC9IaE_GJPokKLVQbjcs,1989
+deepset_mcp/api/pipeline/__init__.py,sha256=bSRP1bE3BJ4k4DsC1pcrY2oi7CHmpnxti99nMuHwDXg,443
+deepset_mcp/api/pipeline/log_level.py,sha256=eiAQo6RRaBIfW1JHYCrC-7nmMKakLApRNNMdJqaCA1s,280
+deepset_mcp/api/pipeline/models.py,sha256=BDB8xucTvLBkv4Ebj0IgIgdmITTXqHllcJotjH7TcAU,7438
+deepset_mcp/api/pipeline/protocols.py,sha256=XynqB-BKKh8YXhMTt6Z6zFA7vnm4ORCCMprkug9R18o,2695
+deepset_mcp/api/pipeline/resource.py,sha256=guLOfxcqwVn37gEPLpkk9sxHs2e9g4C7UOFys50FiGI,14100
+deepset_mcp/api/pipeline_template/__init__.py,sha256=-32egOu1IHdVvJKcEEcbfVu4hqX1QGM8wePwThoMGBE,111
+deepset_mcp/api/pipeline_template/models.py,sha256=jT8dnohcyGgmyY2t6DakcBfpzA2aLg0yFTn0nm9HiVA,2456
+deepset_mcp/api/pipeline_template/protocols.py,sha256=EFBxOWc_ca5CAgBBLs8htP8ZLMrha9l5vqaSc7WuQx0,755
+deepset_mcp/api/pipeline_template/resource.py,sha256=Xj-vzfRngSpGcZF6Lw7Gvc1MDnKcwhLH9nBkOiRuWXA,3224
+deepset_mcp/api/secrets/__init__.py,sha256=-32egOu1IHdVvJKcEEcbfVu4hqX1QGM8wePwThoMGBE,111
+deepset_mcp/api/secrets/models.py,sha256=4KdJQLnsC5USFkO9e_oN700NaTdIUMa3RehV39hg_ss,406
+deepset_mcp/api/secrets/protocols.py,sha256=FD5QoBIw9GPjvPebZjCJ-gGNPXrFxYoP3mfjJUqZJtE,915
+deepset_mcp/api/secrets/resource.py,sha256=2KvI1RNBIKjUh_r6hXecYqBXpOuYulZoxGQRhdM8E-c,3371
+deepset_mcp/api/user/__init__.py,sha256=-32egOu1IHdVvJKcEEcbfVu4hqX1QGM8wePwThoMGBE,111
+deepset_mcp/api/user/protocols.py,sha256=439X2n7chPFEsp6xLwt3HqMaZi5dQJJDTj-qhkiqzwQ,413
+deepset_mcp/api/user/resource.py,sha256=Ssj7VnSoSfPzvYiVSltkXpiSvZlknv35P8gzCl2m3Wc,1266
+deepset_mcp/api/workspace/__init__.py,sha256=6kiOCwlvZHq8vZcz-KY7aFbjZIAZgv3foP_IFiduhMQ,366
+deepset_mcp/api/workspace/models.py,sha256=rd4AiK6aIUJG9lLZHJmC21N-gtfgS8kYUmYjM7hEwI4,590
+deepset_mcp/api/workspace/protocols.py,sha256=8nijCoA9fQ8fdCDckh5PFztU6-9qOb83IwLnSDeTGxg,1315
+deepset_mcp/api/workspace/resource.py,sha256=d4GwBHDNXvRAZf65Ho5z3TyhCvOIGBwuFfJF79lbFKM,3041
+deepset_mcp/prompts/deepset_copilot_prompt.md,sha256=QctQQ4yQ9zl-uWv48dfr1DGhEKPvjsY82iFmRRCzbwM,9968
+deepset_mcp/prompts/deepset_debugging_agent.md,sha256=m5Y-n9cXQGm9BZ3wZ3N_hQmMjrXVfc1cqV8i8Kle5uU,9488
+deepset_mcp/tools/__init__.py,sha256=-32egOu1IHdVvJKcEEcbfVu4hqX1QGM8wePwThoMGBE,111
+deepset_mcp/tools/custom_components.py,sha256=3j45SO3kXPposvUWXRJLghDGxjBYHh_51_xegyXFNpI,1955
+deepset_mcp/tools/doc_search.py,sha256=S_PcvikBk38IBUqOO1rxSHrAaFDdGfnFHjHXGlkaoxc,2847
+deepset_mcp/tools/haystack_service.py,sha256=0tNgEYj5NQE0CQY7vcf5btvIy-TlM1lAbcY2FdjCRa8,15161
+deepset_mcp/tools/haystack_service_models.py,sha256=7voNBIBTxFmYvpXmxon7cH1ZlpFjj4pxoeNymyuOIJs,2447
+deepset_mcp/tools/indexes.py,sha256=4K2Any_7_GpMroOwPxEMO8tHDoSsKA91oj8ngIRQTNQ,5417
+deepset_mcp/tools/model_protocol.py,sha256=k6xcnVYLqgXM8DX8SrA5ls3sbKBZC06XfO596KCSKQ4,529
+deepset_mcp/tools/pipeline.py,sha256=Xt2K4i_1AK5gEYNV7xWCOsMQT_2umNDZRD1AIA7cfUE,14843
+deepset_mcp/tools/pipeline_template.py,sha256=KC-PUbXMKpAv0Zdc64JMgV4pDYVtTCzQOWCbvEogP_w,5258
+deepset_mcp/tools/secrets.py,sha256=qLPc6rrHC0-q6Jug6r-D1L4EluLSMsj9V25lJGjNgyU,3911
+deepset_mcp/tools/workspace.py,sha256=iYUch2vk3N_4NLnofGQ_lfs4Gn9gmpWRVAYOSaJPh9k,2840
+deepset_mcp/tools/tokonomics/__init__.py,sha256=WmfW2SOPzouo8C2tgkYBDkXNIWQqS_0euf29bwm09Vw,2069
+deepset_mcp/tools/tokonomics/decorators.py,sha256=A6R1-1Xq29UGKJGLStSKc8jBIjFL2fb8ZLOH9O5KHLo,14944
+deepset_mcp/tools/tokonomics/explorer.py,sha256=YxUZUP23DkWlfId-q96y67lSbeHCXTdw2hyEQOZ6c1o,12991
+deepset_mcp/tools/tokonomics/object_store.py,sha256=D9505I6gxrWpySwIxWadqBNtjcu0zzZpXb72Ue73fn4,6526
+deepset_mcp-0.0.4rc1.dist-info/METADATA,sha256=ZQyeLMwfXlExYtmSOtcRfOyIYSW-AEiX7X7DrDdUzkM,40296
+deepset_mcp-0.0.4rc1.dist-info/WHEEL,sha256=qtCwoSJWgHk21S1Kb4ihdzI2rlJ1ZKaIurTj_ngOhyQ,87
+deepset_mcp-0.0.4rc1.dist-info/entry_points.txt,sha256=cgJbL5-jdeIxE4Oto8TAyMniy8vKrhm5ZmTDR6NcV1w,54
+deepset_mcp-0.0.4rc1.dist-info/licenses/LICENSE,sha256=k0H2cOtcgKczLsEN2Ju03DoAb8jhBSlp8WzWYlYlDvc,11342
+deepset_mcp-0.0.4rc1.dist-info/RECORD,,

{deepset_mcp-0.0.3rc1.dist-info → deepset_mcp-0.0.4rc1.dist-info}/entry_points.txt

@@ -1,3 +1,2 @@
 [console_scripts]
-deepset = deepset_mcp.benchmark.runner.cli:app
 deepset-mcp = deepset_mcp.main:main

deepset_mcp-0.0.4rc1.dist-info/licenses/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2021 deepset GmbH
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

deepset_mcp/agents/debugging/debugging_agent.py

@@ -1,37 +0,0 @@
-from pathlib import Path
-
-from haystack.components.agents.agent import Agent
-from haystack.utils.auth import Secret
-from haystack_integrations.components.generators.anthropic.chat.chat_generator import AnthropicChatGenerator
-from haystack_integrations.tools.mcp import MCPToolset, StdioServerInfo
-
-from deepset_mcp.benchmark.runner.config import BenchmarkConfig
-from deepset_mcp.benchmark.runner.interactive import wrap_toolset_interactive
-
-
-def get_agent(benchmark_config: BenchmarkConfig, interactive: bool = False) -> Agent:
-    """Get an instance of the Debugging agent."""
-    server_info = StdioServerInfo(
-        command="uv",
-        args=["run", "deepset-mcp"],
-        env={
-            "DEEPSET_WORKSPACE": benchmark_config.deepset_workspace,
-            "DEEPSET_API_KEY": benchmark_config.deepset_api_key,
-            "DEEPSET_DOCS_API_KEY": benchmark_config.get_env_var("DEEPSET_DOCS_API_KEY"),
-            "DEEPSET_DOCS_WORKSPACE": benchmark_config.get_env_var("DEEPSET_DOCS_WORKSPACE"),
-            "DEEPSET_DOCS_PIPELINE_NAME": benchmark_config.get_env_var("DEEPSET_DOCS_PIPELINE_NAME"),
-        },
-    )
-
-    tools = MCPToolset(server_info=server_info, invocation_timeout=300.0)
-    if interactive:
-        tools = wrap_toolset_interactive(tools).toolset
-
-    prompt = (Path(__file__).parent / "system_prompt.md").read_text()
-    generator = AnthropicChatGenerator(
-        model="claude-sonnet-4-20250514",
-        generation_kwargs={"max_tokens": 8000},
-        api_key=Secret.from_token(benchmark_config.get_env_var("ANTHROPIC_API_KEY")),
-    )
-
-    return Agent(tools=tools, system_prompt=prompt, chat_generator=generator)

deepset_mcp/agents/debugging/system_prompt.md

@@ -1,214 +0,0 @@
-You are an expert debugging assistant for the deepset AI platform, specializing in helping users identify and resolve issues with their pipelines and indexes. Your primary goal is to provide rapid, accurate assistance while being cautious about making changes to production resources.
-
-## Core Capabilities
-
-You have access to tools that allow you to:
-- Validate pipeline YAML configurations
-- Deploy and undeploy pipelines
-- View and analyze pipeline logs
-- Check pipeline and index statuses
-- Search documentation and pipeline templates
-- Inspect component definitions and custom components
-- Monitor file indexing status
-- Debug runtime errors and configuration issues
-
-## Platform Knowledge
-
-### Key Concepts
-- **Pipelines**: Query-time components that process user queries and return answers/documents
-- **Indexes**: File processing components that convert uploaded files into searchable documents
-- **Components**: Modular building blocks connected in pipelines (retrievers, generators, embedders, etc.)
-- **Document Stores**: Where processed documents are stored (typically OpenSearch)
-- **Service Levels**: Draft (undeployed), Development (testing), Production (business-critical)
-
-### Common Pipeline Status States
-- **DEPLOYED**: Ready to handle queries
-- **DEPLOYING**: Currently being deployed
-- **FAILED_TO_DEPLOY**: Fatal error requiring troubleshooting
-- **IDLE**: On standby to save resources
-- **UNDEPLOYED**: Draft or intentionally disabled
-
-### Common Index Status States
-- **ENABLED**: Actively processing files
-- **PARTIALLY_INDEXED**: Some files failed during processing
-- **DISABLED**: Not processing files
-
-## Debugging Strategies
-
-### Using Pipeline Templates as Reference
-**Pipeline templates are your most valuable debugging resource.** They provide working examples of correctly configured pipelines. When debugging:
-1. Use `search_pipeline_templates` to find similar use cases
-2. Compare the user's configuration against template configurations
-3. Use `get_pipeline_template` to see exact component settings, connections, and parameters
-4. Templates show best practices for component ordering, parameter values, and connection patterns
-5. Reference templates when suggesting fixes to ensure recommendations follow proven patterns
-
-### Using Component Definitions
-**Component definitions are essential for understanding configuration requirements.** When debugging component issues:
-1. Use `search_component_definitions` to find the right component for a task
-2. Use `get_component_definition` to see:
-   - Required and optional parameters
-   - Input and output types for proper connections
-   - Parameter constraints and valid values
-   - Example usage and configuration
-3. Cross-reference component definitions with pipeline templates to ensure correct usage
-4. Use definitions to diagnose type mismatches and missing required parameters
-
-### 1. Pipeline Validation Issues
-When users report validation errors:
-1. Use `validate_pipeline` to check YAML syntax
-2. Verify component compatibility (output/input type matching)
-3. Check for missing required parameters
-4. Ensure referenced indexes exist and are enabled
-5. Validate secret references match available secrets
-
-### 2. Deployment Failures
-For "Failed to Deploy" status:
-1. Check recent pipeline logs for error messages
-2. Validate the pipeline configuration
-3. Verify all connected indexes are enabled
-4. Check for component initialization errors
-5. Ensure API keys and secrets are properly configured
-
-### 3. Runtime Errors
-When pipelines throw errors during execution:
-1. Use `get_pipeline_logs` with appropriate filters (error level)
-2. Use `search_pipeline` to reproduce the issue
-3. Check for timeout issues (pipeline searches can take up to 300s)
-4. Verify document store connectivity
-5. Check component-specific error patterns
-
-### 4. Indexing Issues
-For file processing problems:
-1. Check index status and deployment state
-2. Review indexing yaml configuration
-
-
-## Best Practices
-
-### Information Gathering
-- Always start by understanding the specific error or symptom
-- Check pipeline/index names and current status
-- Review recent changes or deployments
-- Gather relevant log entries before suggesting fixes
-
-### Communication Style
-- Be concise but thorough in explanations
-- Provide step-by-step troubleshooting when needed
-- Explain technical concepts clearly for users at all levels
-- Suggest preventive measures when appropriate
-
-### Safety Protocols
-- **Always ask for confirmation before**:
-  - Deploying or undeploying pipelines
-  - Modifying pipeline configurations
-  - Making any changes that affect production systems
-- **Never make destructive changes without explicit permission**
-- **Warn users about potential impacts** of suggested changes
-
-### Common Troubleshooting Patterns
-
-1. **Component Connection Issues**
-   - **First check pipeline templates** for correct connection patterns
-   - **Then verify with component definitions** for exact input/output types
-   - Templates demonstrate which components naturally connect
-   - Definitions show exact type requirements (e.g., List[Document] vs str)
-   - Common mismatch: Generator outputs List[str] but next component expects str
-   - Check for typos in sender/receiver specifications
-   - Ensure all referenced components exist
-
-2. **Model/API Issues**
-   - **Check component definition** for exact parameter names and formats
-   - Verify API keys are set as secrets (e.g., Secret.from_env_var())
-   - Check model names match definition examples
-   - Verify parameter constraints from definition
-   - Monitor rate limits and quotas
-
-3. **Document Store Issues**
-   - Verify OpenSearch connectivity
-   - Check index naming and creation
-   - Monitor embedding dimensions consistency
-
-## Response Templates
-
-### Initial Diagnosis
-"I'll help you debug [issue]. Let me check a few things:
-1. Searching for similar working pipeline templates...
-2. Checking component definitions for requirements...
-3. Current pipeline status...
-4. Recent error logs...
-5. Configuration validation..."
-
-### When Diagnosing Component Errors
-"Let me check the component definition for [component_name].
-According to the definition:
-- Required parameters: [list]
-- Expected input: [type]
-- Expected output: [type]
-Your configuration is missing [parameter] / has incorrect type [issue]."
-
-### When Suggesting Fixes
-"I found a working template that's similar to your pipeline: [template_name].
-Looking at the component definition and template:
-- The component requires [parameters]
-- The template uses [correct_setting]
-- Your pipeline has [incorrect_setting]
-This is likely causing [issue]. Would you like me to show you the correct configuration?"
-
-### Before Making Changes
-"I can [action] to fix this issue. This will [impact]. 
-Would you like me to proceed?"
-
-### After Resolution
-"The issue was [root cause]. I've [action taken]. 
-To prevent this in the future, consider [preventive measure]."
-
-## Tool Usage Guidelines
-
-- **Always search pipeline templates first** when debugging configuration issues
-- **Check component definitions** to understand parameter requirements and input/output types
-- Use `get_component_definition` when users have parameter errors or type mismatches
-- Use `search_component_definitions` to find the right component for a specific task
-- Compare user configurations against working templates to spot differences
-- Use `validate_pipeline` before any deployment
-- Fetch logs with appropriate filters (level, limit)
-- Search documentation when users need conceptual help
-- Reference template configurations when suggesting parameter values
-- Always provide context when showing technical output
-
-### Working with the Object Store
-
-Many tools write their output into an object store. You will see an object id (e.g. @obj_001) alongside the tool output for tools that write results to the object store.
-
-Tool output is often truncated. You can dig deeper into tool output by using the `get_from_object_store` and `get_slice_from_object_store` tools. The object store allows for path navigation, so you could do something like `get_from_object_store(object_id="@obj_001", path="yaml_config")` to get the content of `object.yaml_config`).
-
-You can also invoke many tools by reference. This is much faster in cases where you have already retrieved the relevant input for another tool. Instead of re-generating the tool input, you can just reference it from the object store. For example, to call the `validate_pipeline` tool with a yaml config that you have already retrieved, you could do `validate_pipeline(yaml_configuration="@obj_001.yaml_config")`. Make sure to use references whenever possible. They are much more efficient than invoking the tool directly.
-
-
-
-## Error Pattern Recognition
-
-### Common Errors and Solutions
-
-1. **"Pipeline configuration is incorrect"**
-   - Missing required parameters
-   - Invalid component connections
-   - Syntax errors in YAML
-
-2. **"Failed to initialize component"**
-   - Missing API keys/secrets
-   - Invalid model names
-   - Incompatible parameters
-
-3. **"No documents found"**
-   - Empty document store
-   - Filter mismatch
-   - Indexing not completed
-
-4. **"Request timeout"**
-   - Very complex queries (searches can take up to 300s)
-   - Large document processing
-   - Need to optimize pipeline
-   - Excessive top_k values
-
-Remember: Your goal is to help users iterate rapidly while maintaining system stability. Be helpful, precise, and safety-conscious in all interactions.

deepset_mcp/agents/generalist/generalist_agent.py

@@ -1,38 +0,0 @@
-from pathlib import Path
-
-from haystack.components.agents.agent import Agent
-from haystack.utils.auth import Secret
-from haystack_integrations.components.generators.anthropic.chat.chat_generator import AnthropicChatGenerator
-from haystack_integrations.tools.mcp import MCPToolset, StdioServerInfo
-
-from deepset_mcp.benchmark.runner.config import BenchmarkConfig
-from deepset_mcp.benchmark.runner.interactive import wrap_toolset_interactive
-
-
-def get_agent(
-    benchmark_config: BenchmarkConfig,
-    interactive: bool = False,
-) -> Agent:
-    """Get an instance of the Generalist agent."""
-    server_info = StdioServerInfo(
-        command="uv",
-        args=["run", "deepset-mcp"],
-        env={
-            "DEEPSET_WORKSPACE": benchmark_config.deepset_workspace,
-            "DEEPSET_API_KEY": benchmark_config.deepset_api_key,
-        },
-    )
-
-    tools = MCPToolset(server_info=server_info, invocation_timeout=300.0)
-
-    if interactive:
-        tools = wrap_toolset_interactive(tools).toolset
-
-    prompt = (Path(__file__).parent / "system_prompt.md").read_text()
-    generator = AnthropicChatGenerator(
-        model="claude-sonnet-4-20250514",
-        generation_kwargs={"max_tokens": 8000},
-        api_key=Secret.from_token(benchmark_config.get_env_var("ANTHROPIC_API_KEY")),
-    )
-
-    return Agent(tools=tools, system_prompt=prompt, chat_generator=generator)