mcs-driver-core 0.2.0__tar.gz → 0.2.2__tar.gz

{mcs_driver_core-0.2.0/src/mcs_driver_core.egg-info → mcs_driver_core-0.2.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mcs-driver-core
-Version: 0.2.0
+Version: 0.2.2
 Summary: Core driver contract for the Model Context Standard.
 Author-email: Danny Gerst <danny@dannygerst.de>
 License-Expression: Apache-2.0

{mcs_driver_core-0.2.0 → mcs_driver_core-0.2.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name            = "mcs-driver-core"
-version         = "0.2.0"
+version         = "0.2.2"
 description     = "Core driver contract for the Model Context Standard."
 readme          = "README.md"
 requires-python = ">=3.9"
@@ -42,3 +42,6 @@ dev = [
 
 [tool.setuptools.packages.find]
 where = ["src"]
+
+[tool.setuptools.package-data]
+"mcs.driver.core" = ["prompts/*.toml"]

{mcs_driver_core-0.2.0 → mcs_driver_core-0.2.2}/src/mcs/driver/core/mcs_tool_driver_interface.py

@@ -49,18 +49,50 @@ class Tool:
     that an external entity (e.g., an orchestrator or an LLM capable of
     tool-calling) can understand and invoke.
 
+    The three-tier identification mirrors both MCP and OpenAPI conventions:
+
+    * ``name``  -- machine identifier (MCP ``name``, OpenAPI ``operationId``)
+    * ``title`` -- short human-readable label (MCP ``title``, OpenAPI ``summary``)
+    * ``description`` -- full text forwarded to the LLM, may contain multi-line
+      prompt-engineering instructions (MCP ``description``, OpenAPI ``description``)
+
+    A client or orchestrator can choose to expose only ``name`` + ``title``
+    to the LLM to save context-window tokens and load the full
+    ``description`` on demand when a tool is actually selected.
+
+    At least one of ``title`` or ``description`` must be provided.
+    When only ``title`` is given, ``description`` is auto-filled from it
+    so that downstream consumers (e.g. ``PromptStrategy.format_tools``)
+    always find a non-empty ``description``.
+
     Attributes
     ----------
     name : str
-        The unique name of the tool, used to identify it.
-    description : str
-         A detailed description of what the tool does and when it should be used.
+        Unique machine-readable identifier for the tool.
+    title : str or None
+        Optional short human-readable label for display and token-efficient
+        tool listings.  Maps to OpenAPI ``summary`` / MCP ``title``.
+    description : str or None
+        Detailed description forwarded to the LLM.  May include usage
+        instructions, constraints and examples.  Auto-filled from
+        ``title`` when not provided explicitly.
     parameters : list[ToolParameter]
-        A list of `Parameter` objects, defining the inputs required by the tool.
+        Inputs required by the tool.
     """
     name: str
-    description: str
-    parameters: list[ToolParameter]
+    title: Optional[str] = None
+    description: Optional[str] = None
+    parameters: list[ToolParameter] = None  # type: ignore[assignment]    
+
+    def __post_init__(self) -> None:
+        if self.parameters is None:
+            self.parameters = []
+        if not self.description and self.title:
+            self.description = self.title
+        if not self.description and not self.title:
+            raise ValueError(
+                f"Tool '{self.name}': at least one of 'title' or 'description' must be provided."
+            )
 
 
 class MCSToolDriver(ABC):

mcs_driver_core-0.2.2/src/mcs/driver/core/prompts/default_json.toml

@@ -0,0 +1,68 @@
+[meta]
+name = "json-default"
+version = "1.0.0"
+
+# ── Prompt Generation ──────────────────────────────────────
+
+[system_message]
+template = """
+You are a helpful assistant with access to these tools:
+
+{tools}
+
+Choose the appropriate tool based on the user's question.
+If no tool is needed, reply directly.
+
+IMPORTANT: When you need to use a tool, respond with ONLY this format:
+{call_example}
+
+After receiving a tool's response:
+1. Transform the raw data into a natural, conversational response
+2. Keep responses concise but informative
+3. Focus on the most relevant information
+4. Use appropriate context from the user's question
+5. Avoid simply repeating the raw data
+
+Please use only the tools that are explicitly defined above.
+If you want to use a tool, ALWAYS reply with the JSON object format.
+"""
+
+[call_example]
+example = """\
+{
+    "tool": "tool-name",
+    "arguments": {
+        "argument-name": "value"
+    }
+}"""
+
+# ── Parsing Configuration ──────────────────────────────────
+
+[parsing]
+tool_field_aliases = ["tool", "name"]
+unknown_tool_behavior = "silent"
+
+# ── Retry Prompts (placeholders: {tool_name}, {available}, {error}) ──
+
+[retry_prompts]
+no_tool_field = "Return a JSON object with a 'tool' field matching one of the available tool names."
+unknown_tool = "No tool '{tool_name}' found. Available tools: {available}."
+execution_failed = "Tool '{tool_name}' execution failed: {error}. Check argument names and value types, then retry."
+
+# ── Healing Rules (regex pairs, applied before the parser) ──
+# New LLM quirks → add a rule here, bump version.
+
+[[healing]]
+pattern = '```\w*\s*\n?'
+replacement = ''
+comment = "Opening markdown fence (```json, ```python, etc.)"
+
+[[healing]]
+pattern = '\n?```\s*$'
+replacement = ''
+comment = "Closing markdown fence"
+
+[[healing]]
+pattern = '``[´`]\w*\s*\n?'
+replacement = ''
+comment = "Known LLM typo: backtick variants"

{mcs_driver_core-0.2.0 → mcs_driver_core-0.2.2/src/mcs_driver_core.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mcs-driver-core
-Version: 0.2.0
+Version: 0.2.2
 Summary: Core driver contract for the Model Context Standard.
 Author-email: Danny Gerst <danny@dannygerst.de>
 License-Expression: Apache-2.0

{mcs_driver_core-0.2.0 → mcs_driver_core-0.2.2}/src/mcs_driver_core.egg-info/SOURCES.txt

@@ -11,6 +11,7 @@ src/mcs/driver/core/mixins/__init__.py
 src/mcs/driver/core/mixins/driver_context_mixin.py
 src/mcs/driver/core/mixins/healthcheck.py
 src/mcs/driver/core/mixins/tool_call_signaling_mixin.py
+src/mcs/driver/core/prompts/default_json.toml
 src/mcs_driver_core.egg-info/PKG-INFO
 src/mcs_driver_core.egg-info/SOURCES.txt
 src/mcs_driver_core.egg-info/dependency_links.txt