{"report":{"v":1,"package":"raidcom-mcp","version":"0.1.8","ranAt":"2026-11-16T11:44:03.456Z","install":{"ok":true,"integrity":"sha512-z5Sp4xdnGekg7E9Vp8KtbagfKfwwWUy8kSpx8UPB9bizAcmHYJBvec2JMbPHwL8p3kzqFizG+j9Ng0qA6JLWdA==","deps":95,"scripts":[],"bins":["raidcom-mcp"],"license":"MIT","engines":"node >=22.19.0","repository":"git+https://github.com/visubramaniam/raidcom-mcp.git","bin":"raidcom-mcp"},"start":{"ok":true,"ms":145,"serverName":"raidcom-mcp","serverVersion":"0.1.8","protocol":"2025-06-18","stderr":"[raidcom-mcp] ready: 178 commands, 14 recipes, build-only\n"},"tools":[{"name":"raidcom_list_commands","description":"Find raidcom commands. Use this first when you do not know the exact command name. With no arguments, lists every object (ldev, lun, host_grp, pool, ...) with the actions available on it. With `query` (plain words, e.g. \"map a volume to a host group\", \"grow a pool\", \"show free ldev ids\"), ranks matching commands and rates the confidence of the top result. With `action` and/or `object`, lists exactly those commands. Then call raidcom_describe_command, or raidcom_build_command if you already know the options.","params":["query","action","object","limit"]},{"name":"raidcom_describe_command","description":"Everything needed to build one raidcom command: what it does, which models support it, whether it is read-only, destructive or asynchronous, each syntax form, every option with the number and kind of values it takes (and the words it accepts, where it accepts only a few), and examples. Call it before raidcom_build_command when you are unsure which options a command needs or which of its syntax forms fits the request.","params":["command","option"]},{"name":"raidcom_build_command","description":"Build one raidcom command from structured arguments and validate it. Nothing is executed and no storage system is contacted: you get command text to review and run elsewhere. Unknown options, wrong value counts, missing required options, bad port names and out-of-range LDEV, LUN, pool and serial numbers are reported as errors with a fix. Example: {\"command\": \"add ldev\", \"options\": {\"-pool\": 0, \"-ldev_id\": 256, \"-capacity\": \"100G\"}, \"model\": \"vsp-one-b28\", \"global\": {\"instance\": 0}} → `raidcom add ldev -pool 0 -ldev_id 256 -capacity 100G -I0`. For many similar commands use raidcom_build_script, not repeated calls. When the user asks for a command, show them the `command` from the result.","params":["command","options","model","global","strict"]},{"name":"raidcom_check_command","description":"Validate and explain a raidcom command line the user already has (for example one pasted from a runbook). It is parsed, not executed: shell operators such as ; | & > are refused. Returns the normalised command, what each option means, and every problem found. Credentials after -login are dropped.","params":["command_line","model","strict"]},{"name":"raidcom_build_script","description":"Build a shell script of raidcom commands from steps. Each step is a command with options, optionally repeated with `foreach` (every combination) or `zip` (values advance together), so \"create LDEVs 100 to 109 in pool 0, then map each to port CL1-A\" is two steps. Every expanded command is validated; the script is returned only if all of them are valid, otherwise you get the errors per step. The script checks each command's exit status, adds `raidcom get command_status` after asynchronous commands, and can lock the resource group and log in (credentials are read from RAIDCOM_USER and RAIDCOM_PASSWORD in the user's shell, never written into the script). Nothing is executed.","params":["steps","model","global","strict","login","lock_resource","description"]},{"name":"raidcom_list_recipes","description":"Ready-made workflows: provision volumes to an FC, iSCSI or NVMe/TCP host, create or grow a pool, create a mainframe (3390) pool, extend or delete volumes, create a command device, reclaim zero pages, read-only inventory, copy groups. With no arguments lists them. With `recipe`, shows its parameters and steps. With `query`, ranks recipes by keyword. Use raidcom_build_recipe to turn one into a script.","params":["recipe","query"]},{"name":"raidcom_build_recipe","description":"Build the script for a recipe from its parameters (see raidcom_list_recipes). Lists such as ldev_ids accept ranges: [\"100-109\"]. Example: recipe provision-fc-volumes with {\"pool\": 0, \"ldev_ids\": [\"100-103\"], \"capacity\": \"100G\", \"ports\": [\"CL1-A\", \"CL2-A\"], \"host_grp\": \"esx01\", \"host_mode\": \"VMWARE_EX\", \"wwns\": [\"210000e08b0256f8\"]}. Returns the script and the individual commands. Nothing is executed.","params":["recipe","params","model","global","strict","login","lock_resource"]},{"name":"raidcom_model_limits","description":"Valid parameter ranges for a storage model (serial number, LDEV ID, pool ID, LU number, port names), taken from the Command Reference appendices. Without `model`, lists the models.","params":["model"]}],"toolsHash":"f60e9b368ab9e491f457ef74b292fbf42b29287ff1672c546c365d32d94d3f39","wrote":[],"callsAt":"2026-11-16T11:44:08.987Z","calls":[{"tool":"raidcom_list_recipes","ok":true,"ms":3,"bytes":2217}],"host":{"commit":"eaaffffaf52255d1b77dc4aacffdfaf353f0c12c","run":"https://github.com/itsHaddad/bragproof/actions/runs/43857070216"},"network":{"names":["registry.npmjs.org"],"conns":[],"callNames":[],"callConns":[]}},"summary":{"outcome":"started","needs":[],"contacts":[],"flags":[],"tools":8,"wrote":0,"callsTried":1,"callsAnswered":1,"callContacts":[]},"history":[{"package":"raidcom-mcp","version":"0.1.8","ranAt":"2026-11-16T11:44:03.456Z","outcome":"started","tools":8,"contacts":0,"flags":0,"serious":0,"toolsHash":"f60e9b368ab9e491f457ef74b292fbf42b29287ff1672c546c365d32d94d3f39"}],"page":"https://bragproof.smaverk.com/r/raidcom-mcp"}