kibi-mcp 0.14.3 → 0.15.0
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.
- package/dist/tools-config.js +3 -2
- package/package.json +3 -3
package/dist/tools-config.js
CHANGED
|
@@ -272,7 +272,7 @@ const BASE_TOOLS = [
|
|
|
272
272
|
},
|
|
273
273
|
{
|
|
274
274
|
name: "kb_upsert",
|
|
275
|
-
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`) 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.",
|
|
275
|
+
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.",
|
|
276
276
|
inputSchema: {
|
|
277
277
|
type: "object",
|
|
278
278
|
required: ["type", "id", "properties"],
|
|
@@ -342,7 +342,7 @@ const BASE_TOOLS = [
|
|
|
342
342
|
},
|
|
343
343
|
relationships: {
|
|
344
344
|
type: "array",
|
|
345
|
-
description: "Optional relationship rows to create in the same call. For requirement encoding, prefer `constrains` + `requires_property`
|
|
345
|
+
description: "Optional relationship rows to create in the same call. For requirement encoding, prefer `constrains` + `requires_property` for strict property facts or `requires_predicate` for ontology predicate facts. Side effect: asserts edges in KB.",
|
|
346
346
|
items: {
|
|
347
347
|
type: "object",
|
|
348
348
|
required: ["type", "from", "to"],
|
|
@@ -360,6 +360,7 @@ const BASE_TOOLS = [
|
|
|
360
360
|
"constrained_by",
|
|
361
361
|
"constrains",
|
|
362
362
|
"requires_property",
|
|
363
|
+
"requires_predicate",
|
|
363
364
|
"guards",
|
|
364
365
|
"publishes",
|
|
365
366
|
"consumes",
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "kibi-mcp",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.15.0",
|
|
4
4
|
"dependencies": {
|
|
5
5
|
"@modelcontextprotocol/sdk": "^1.26.0",
|
|
6
6
|
"ajv": "^8.18.0",
|
|
@@ -9,8 +9,8 @@
|
|
|
9
9
|
"fast-glob": "^3.2.12",
|
|
10
10
|
"gray-matter": "^4.0.3",
|
|
11
11
|
"js-yaml": "^4.1.0",
|
|
12
|
-
"kibi-cli": "^0.
|
|
13
|
-
"kibi-core": "^0.
|
|
12
|
+
"kibi-cli": "^0.12.0",
|
|
13
|
+
"kibi-core": "^0.6.0",
|
|
14
14
|
"mcpcat": "^0.1.12",
|
|
15
15
|
"ts-morph": "^23.0.0",
|
|
16
16
|
"zod": "^4.3.6"
|