Fix ERP lager MCP schema properties
This commit is contained in:
1 parent
1b7e0c8a13
commit
84a4e6ac63
3 files changed
+4
-1
No files matched your search
@@ -27,3 +27,5 @@ Das Interface ist ausschließlich lesend. Es gibt keine Lager-MCP-Tools zum Anle
|
||||
## JSON-RPC
|
||||
|
||||
Das Interface unterstützt `initialize`, `notifications/initialized`, `tools/list` und `tools/call` gemäß dem bestehenden Marktmanagement-MCP-Transport.
|
||||
|
||||
Bei `tools/list` ist `inputSchema.properties` für jedes Werkzeug immer ein JSON-Objekt; beim parameterlosen `erp_lager.list_products` ist es `{}`.
|
||||
@@ -34,7 +34,7 @@ function erp_lager_mcp_tools(): array
|
||||
[
|
||||
'name' => 'erp_lager.list_products',
|
||||
'description' => 'Aktive ERP-Lagerprodukte zur Ermittlung der Produkt-IDs lesen',
|
||||
'inputSchema' => ['type' => 'object', 'properties' => []],
|
||||
'inputSchema' => ['type' => 'object', 'properties' => (object) []],
|
||||
],
|
||||
[
|
||||
'name' => 'erp_lager.get_product',
|
||||
|
||||
@@ -20,4 +20,5 @@ assert_test($names === ['erp_lager.list_products', 'erp_lager.get_product'], 'Un
|
||||
$productTool = $tools[1];
|
||||
assert_test($productTool['inputSchema']['required'] === ['product_id'], 'Product detail tool must require product_id');
|
||||
assert_test($productTool['inputSchema']['properties']['product_id']['type'] === 'integer', 'Product ID must be an integer');
|
||||
assert_test(is_object($tools[0]['inputSchema']['properties']), 'List products properties must serialize as a JSON object');
|
||||
fwrite(STDOUT, "erp_lager_mcp_tools_list_test: OK\n");
|
||||
Reference in new issue
Block a user