kibi-mcp 0.16.0 → 0.17.2

package/dist/tools-config.js

@@ -270,9 +270,67 @@ const BASE_TOOLS = [
             },
         },
     },
+    {
+        name: "kb_sparql_remote",
+        description: "Opt-in remote SPARQL query tool for external HTTP(S) RDF endpoints. This does not query Kibi's local RDF store directly, stores no credentials, and depends on network availability.",
+        inputSchema: {
+            type: "object",
+            required: ["endpoint", "query"],
+            properties: {
+                endpoint: {
+                    type: "string",
+                    description: "Remote SPARQL endpoint URL. Must start with http:// or https://.",
+                },
+                query: {
+                    type: "string",
+                    description: "SPARQL SELECT query to send to the remote endpoint.",
+                },
+                timeoutMs: {
+                    type: "number",
+                    description: "Optional positive timeout in milliseconds for the remote query.",
+                },
+            },
+        },
+    },
+    {
+        name: "kb_semantic_advisor",
+        description: "Analyze requirement prose without mutating the KB and return semantic advisor receipts with modeling suggestions. Use before constructing kb_upsert payloads when prose may contain machine-checkable logic. Suggestions can include strict-property facts, predicate facts, ambiguity observations, or ontology-gap observations; all suggestions are advisory and reviewable.",
+        inputSchema: {
+            type: "object",
+            required: ["text"],
+            properties: {
+                text: {
+                    type: "string",
+                    description: "Requirement prose to inspect for machine-checkable modeling suggestions.",
+                },
+                type: {
+                    type: "string",
+                    enum: ["req"],
+                    default: "req",
+                    description: "Entity type context for analysis. Currently requirement prose is supported.",
+                },
+                id: {
+                    type: "string",
+                    description: "Optional requirement ID used for deterministic draft relationship guidance.",
+                },
+                title: {
+                    type: "string",
+                    description: "Optional requirement title for draft apply plans.",
+                },
+                source: {
+                    type: "string",
+                    description: "Optional provenance for draft suggestions.",
+                },
+                status: {
+                    type: "string",
+                    description: "Optional requirement status for draft suggestions.",
+                },
+            },
+        },
+    },
     {
         name: "kb_upsert",
-        description: "Create or update one entity and optional relationships. Use for KB mutations after validating intent. Use the `relationships` array for batch creation of multiple links in a single call (e.g., linking a requirement to multiple tests or facts). Prefer modeling requirements as reusable fact links (`constrains`, `requires_property`, or `requires_predicate`) so consistency and contradiction checks remain queryable. Relationship endpoints must already exist in KB. For requirements, the write will be rejected if it contradicts existing current requirements that constrain the same subject with incompatible properties. To replace a conflicting requirement, include a `supersedes` relationship from the new requirement to the old one in the same request. Do not use for read-only inspection. Side effects: writes KB, may refresh symbol coordinates.",
+        description: "Create or update one entity and optional relationships. Use for KB mutations after validating intent; prefer kb_validate_upsert first because it returns semantic advisor receipts for prose-heavy requirements. Use kb_model_requirement before hand-writing strict property facts from prose, and kb_suggest_predicates before hand-writing ontology predicate facts. Use the `relationships` array for batch creation of multiple links in a single call (e.g., linking a requirement to multiple tests or facts). Prefer modeling requirements as reusable fact links (`constrains`, `requires_property`, or `requires_predicate`) so consistency and contradiction checks remain queryable. Relationship endpoints must already exist in KB. For requirements, the write will be rejected if it contradicts existing current requirements that constrain the same subject with incompatible properties. To replace a conflicting requirement, include a `supersedes` relationship from the new requirement to the old one in the same request. Successful writes may return non-blocking semantic advisor warnings; inspect and repair those warnings before treating prose as contradiction-checkable. Do not use for read-only inspection. Side effects: writes KB, may refresh symbol coordinates.",
         inputSchema: {
             type: "object",
             required: ["type", "id", "properties"],
@@ -351,6 +409,18 @@ const BASE_TOOLS = [
                             ],
                             description: "Optional justification for a coarse file/module-level symbol traceability relationship when narrower function/class/type symbols exist.",
                         },
+                        symbol_role: {
+                            type: "string",
+                            enum: [
+                                "behavioral",
+                                "structural",
+                                "type-shape",
+                                "config",
+                                "module",
+                                "unknown",
+                            ],
+                            description: "Optional role classification for symbol entities. Example: 'behavioral'.",
+                        },
                         fact_kind: {
                             type: "string",
                             enum: [
@@ -361,15 +431,15 @@ const BASE_TOOLS = [
                                 "predicate_schema",
                                 "predicate",
                             ],
-                            description: "Optional fact lane kind for fact entities. Strict lane uses 'subject' and 'property_value'; context lane uses 'observation' or 'meta'.",
+                            description: "Optional fact lane kind for fact entities. Strict lane uses 'subject' and 'property_value'; context lane uses 'observation' or 'meta'; ontology lane uses 'predicate_schema' or 'predicate'. Use kb_model_requirement or kb_suggest_predicates when starting from prose.",
                         },
                         subject_key: {
                             type: "string",
-                            description: "Optional canonical subject key for strict fact entities. Example: 'user.session'.",
+                            description: "Snake_case only. Optional canonical subject key for strict fact entities. Example: 'user.session'. Do not use subjectKey in kb_upsert.properties.",
                         },
                         property_key: {
                             type: "string",
-                            description: "Optional canonical property key for property_value facts. Example: 'session.timeout_minutes'.",
+                            description: "Snake_case only. Optional canonical property key for property_value facts. Example: 'session.timeout_minutes'. Do not use propertyKey in kb_upsert.properties.",
                         },
                         operator: {
                             type: "string",
@@ -379,7 +449,7 @@ const BASE_TOOLS = [
                         value_type: {
                             type: "string",
                             enum: ["string", "int", "number", "bool"],
-                            description: "Optional typed value discriminator for property_value facts.",
+                            description: "Optional typed value discriminator for property_value facts. Pair with exactly one value_string, value_int, value_number, or value_bool; do not use generic value.",
                         },
                         value_string: {
                             type: "string",
@@ -420,12 +490,12 @@ const BASE_TOOLS = [
                         },
                         predicate_name: {
                             type: "string",
-                            description: "Optional predicate name for ontology predicate facts.",
+                            description: "Optional predicate name for ontology predicate facts. Prefer kb_suggest_predicates before hand-writing predicate_name.",
                         },
                         predicate_args: {
                             type: "array",
                             items: { type: "string" },
-                            description: "Optional ordered predicate arguments for ontology predicate facts.",
+                            description: "Optional ordered predicate arguments for ontology predicate facts. Prefer kb_suggest_predicates before hand-writing predicate_args.",
                         },
                     },
                     required: ["title", "status"],
@@ -473,6 +543,38 @@ const BASE_TOOLS = [
             },
         },
     },
+    {
+        name: "kb_validate_upsert",
+        description: "Validate a kb_upsert payload without mutating the KB. Use this read-only preflight before kb_upsert, especially for requirements, because it returns schema/modeling errors plus semantic advisor receipts that identify prose likely needing kb_model_requirement, kb_suggest_predicates, ambiguity review, or an ontology-gap observation.",
+        inputSchema: {
+            type: "object",
+            required: ["type", "id", "properties"],
+            properties: {
+                type: {
+                    type: "string",
+                    enum: [
+                        "req",
+                        "scenario",
+                        "test",
+                        "adr",
+                        "flag",
+                        "event",
+                        "symbol",
+                        "fact",
+                    ],
+                },
+                id: { type: "string" },
+                properties: {
+                    type: "object",
+                    description: "Entity properties to validate using the same snake_case field names accepted by kb_upsert.",
+                },
+                relationships: {
+                    type: "array",
+                    items: { type: "object" },
+                },
+            },
+        },
+    },
     {
         name: "kb_delete",
         description: "Delete entities by ID. Use only for intentional removals after dependency checks. Do not use as a bulk cleanup shortcut. Side effects: mutates and saves KB; skips entities with dependents.",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kibi-mcp",
-  "version": "0.16.0",
+  "version": "0.17.2",
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.26.0",
     "ajv": "^8.18.0",
@@ -9,8 +9,8 @@
     "fast-glob": "^3.2.12",
     "gray-matter": "^4.0.3",
     "js-yaml": "^4.1.0",
-    "kibi-cli": "^0.12.4",
-    "kibi-core": "^0.6.0",
+    "kibi-cli": "^0.12.7",
+    "kibi-core": "^0.6.2",
     "mcpcat": "^0.1.12",
     "ts-morph": "^23.0.0",
     "zod": "^4.3.6"
@@ -27,7 +27,10 @@
     "build": "tsc -p tsconfig.json",
     "prepack": "npm run build"
   },
-  "files": ["dist", "bin"],
+  "files": [
+    "dist",
+    "bin"
+  ],
   "engines": {
     "node": ">=18",
     "bun": ">=1.0"