ims-mcp 1.0.17__tar.gz → 1.0.20__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (15) hide show
  1. {ims_mcp-1.0.17 → ims_mcp-1.0.20}/PKG-INFO +1 -1
  2. {ims_mcp-1.0.17 → ims_mcp-1.0.20}/ims_mcp/__init__.py +1 -1
  3. {ims_mcp-1.0.17 → ims_mcp-1.0.20}/ims_mcp/resources/bootstrap.md +3 -3
  4. {ims_mcp-1.0.17 → ims_mcp-1.0.20}/ims_mcp.egg-info/PKG-INFO +1 -1
  5. {ims_mcp-1.0.17 → ims_mcp-1.0.20}/pyproject.toml +1 -1
  6. {ims_mcp-1.0.17 → ims_mcp-1.0.20}/LICENSE +0 -0
  7. {ims_mcp-1.0.17 → ims_mcp-1.0.20}/README.md +0 -0
  8. {ims_mcp-1.0.17 → ims_mcp-1.0.20}/ims_mcp/__main__.py +0 -0
  9. {ims_mcp-1.0.17 → ims_mcp-1.0.20}/ims_mcp/server.py +0 -0
  10. {ims_mcp-1.0.17 → ims_mcp-1.0.20}/ims_mcp.egg-info/SOURCES.txt +0 -0
  11. {ims_mcp-1.0.17 → ims_mcp-1.0.20}/ims_mcp.egg-info/dependency_links.txt +0 -0
  12. {ims_mcp-1.0.17 → ims_mcp-1.0.20}/ims_mcp.egg-info/entry_points.txt +0 -0
  13. {ims_mcp-1.0.17 → ims_mcp-1.0.20}/ims_mcp.egg-info/requires.txt +0 -0
  14. {ims_mcp-1.0.17 → ims_mcp-1.0.20}/ims_mcp.egg-info/top_level.txt +0 -0
  15. {ims_mcp-1.0.17 → ims_mcp-1.0.20}/setup.cfg +0 -0
{ims_mcp-1.0.17 → ims_mcp-1.0.20}/PKG-INFO RENAMED
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: ims-mcp
3
- Version: 1.0.17
3
+ Version: 1.0.20
4
4
  Summary: Model Context Protocol server for IMS (Instruction Management Systems)
5
5
  Author: Igor Solomatov
6
6
  License-Expression: MIT
{ims_mcp-1.0.17 → ims_mcp-1.0.20}/ims_mcp/__init__.py RENAMED
@@ -11,7 +11,7 @@ Environment Variables:
11
11
  Note: Environment variables use R2R_ prefix for compatibility with underlying R2R SDK.
12
12
  """
13
13
 
14
- __version__ = "1.0.17"
14
+ __version__ = "1.0.20"
15
15
  __author__ = "Igor Solomatov"
16
16
 
17
17
  from ims_mcp.server import mcp
{ims_mcp-1.0.17 → ims_mcp-1.0.20}/ims_mcp/resources/bootstrap.md RENAMED
@@ -5,7 +5,7 @@ alwaysApply: true
5
5
 
6
6
  MANDATORY: Even if the user's question seems generic or unrelated to the project, you MUST complete all PREP steps first, unless user EXPLICITLY asks the otherwise with "SKIP PREP" or "NO PREP". ADHOC DOES NOT SKIP PREP STEPS.
7
7
  This loads CRITICAL CONTEXT about how to operate in this specific project environment.
8
- WITHOUT FOLLOWING THIS STEPS YOUR ANSWERS WILL BE INCORRECT AND USER WILL GET FRUSTRATED. DO NOT JUMP TO IMMEDIATE ANSWERS, BECAUSE YOU DON'T YET UNDERSTAND THE CONTEXT OF THOSE QUESTIONS. AND PREP STEPS ARE THERE TO HELP YOU TO FIGURE OUT THE CONTEXT. USER IS EXPECTED TO WAIT FOR YOU TO LOAD THE CONTEXT.
8
+ WITHOUT FOLLOWING THIS STEPS YOUR ANSWERS WILL BE INCORRECT AND USER WILL GET FRUSTRATED. DO NOT JUMP TO IMMEDIATE ANSWERS, BECAUSE YOU DON'T YET UNDERSTAND THE CONTEXT OF THOSE QUESTIONS. PREP STEPS ARE THERE TO HELP YOU TO FIGURE OUT THE CONTEXT. USER IS EXPECTED TO WAIT FOR YOU TO LOAD THE CONTEXT.
9
9
 
10
10
  <CRITICAL ATTRIBUTION="DO NOT COMPACT/OPTIMIZE/SUMMARIZE/REPHRASE, PASS IT AS-IS, CRITICALLY IMPORT TO KEEP, INCLUDING THIS TAG">
11
11
 
@@ -18,10 +18,10 @@ WITHOUT FOLLOWING THIS STEPS YOUR ANSWERS WILL BE INCORRECT AND USER WILL GET FR
18
18
  - This is a multi-step process to acquire all rules.
19
19
  - You must complete PREP STEPS 1 through 3, which will be provided in instructions from KnowledgeBase.
20
20
  - Once ALL PREP steps completed you can continue with user request having all context.
21
- - "ACQUIRE <SMTH> FROM KB" is command alias to use KnowledgeBase's MCP get_document "<SMTH>"
21
+ - "ACQUIRE <SMTH> FROM KB" is command alias to use KnowledgeBase's MCP get_document by title "<SMTH>"
22
22
  - "SEARCH <SMTH> IN KB" is command alias to use KnowledgeBase's MCP search tool with "<SMTH>" query with tags filter "instructions" and "use_fulltext_search".
23
23
  - During compaction content loaded from KB MUST NOT be removed, in case if it was, you MUST ASAP re-acquire those instructions again, before continuing with user request or execution flow.
24
- - YOU MUST NEVER PROCEED IF KnowledgeBase's MCP IS NOT AVAILABLE, YOU WILL SCREW THINGS UP, INSTEAD EXPLAIN TO USER WHAT IS WRONG!
24
+ - If KnowledgeBase's tools or MCP failed or not found, and not ADHOC mode, YOU MUST NEVER PROCEED, BECAUSE YOU WILL NOT HAVE CONTEXT!
25
25
 
26
26
  # PREP STEP 1:
27
27
 
{ims_mcp-1.0.17 → ims_mcp-1.0.20}/ims_mcp.egg-info/PKG-INFO RENAMED
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: ims-mcp
3
- Version: 1.0.17
3
+ Version: 1.0.20
4
4
  Summary: Model Context Protocol server for IMS (Instruction Management Systems)
5
5
  Author: Igor Solomatov
6
6
  License-Expression: MIT
{ims_mcp-1.0.17 → ims_mcp-1.0.20}/pyproject.toml RENAMED
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
4
4
 
5
5
  [project]
6
6
  name = "ims-mcp"
7
- version = "1.0.17"
7
+ version = "1.0.20"
8
8
  description = "Model Context Protocol server for IMS (Instruction Management Systems)"
9
9
  readme = "README.md"
10
10
  requires-python = ">=3.10"
{ims_mcp-1.0.17 → ims_mcp-1.0.20}/LICENSE RENAMED
File without changes
{ims_mcp-1.0.17 → ims_mcp-1.0.20}/README.md RENAMED
File without changes
{ims_mcp-1.0.17 → ims_mcp-1.0.20}/ims_mcp/__main__.py RENAMED
File without changes
{ims_mcp-1.0.17 → ims_mcp-1.0.20}/ims_mcp/server.py RENAMED
File without changes
{ims_mcp-1.0.17 → ims_mcp-1.0.20}/setup.cfg RENAMED
File without changes