Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
RAIDCOM_LIMITSNoUse another model-limits spec file.bundled
RAIDCOM_CATALOGNoUse another catalogue spec file.bundled
RAIDCOM_RECIPESNoUse another recipes spec file.bundled
RAIDCOM_EXAMPLESNoUse another examples spec file; an empty value turns the example questions off.bundled
RAIDCOM_HTTP_HOSTNoAddress to listen on when using HTTP transport.127.0.0.1
RAIDCOM_HTTP_OPENNoServe anyone who can reach the port, without a token.false
RAIDCOM_HTTP_PORTNoPort to listen on when using HTTP transport (`0` picks a free one).8361
RAIDCOM_TRANSPORTNoTransport for the MCP server: `stdio` or `http`.stdio
RAIDCOM_HTTP_TOKENNoBearer token, at least 32 characters. Required unless `RAIDCOM_HTTP_OPEN=true`.none
RAIDCOM_HTTP_TLS_KEYNoPEM key file; when set with `RAIDCOM_HTTP_TLS_CERT`, the server speaks HTTPS.none
RAIDCOM_HTTP_TLS_CERTNoPEM certificate file; when set with `RAIDCOM_HTTP_TLS_KEY`, the server speaks HTTPS.none
RAIDCOM_HTTP_RATE_LIMITNoRequests per minute per client (`0` for none).120
RAIDCOM_HTTP_TRUST_PROXYNoTake the client address from `X-Forwarded-For`.false
RAIDCOM_HTTP_ALLOWED_HOSTSNoExtra `Host` values to accept (`*` for any).none
RAIDCOM_HTTP_ALLOWED_ORIGINSNo`Origin` values to accept (`*` for any).none
RAIDCOM_HTTP_BEHIND_TLS_PROXYNoA proxy or load balancer ends TLS. Needed for non-loopback addresses without TLS.false

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}
prompts
{}
resources
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
raidcom_list_commandsA

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.

raidcom_describe_commandA

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.

raidcom_build_commandA

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.

raidcom_check_commandA

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.

raidcom_build_scriptA

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.

raidcom_list_recipesA

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.

raidcom_build_recipeA

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.

raidcom_model_limitsA

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.

Prompts

Interactive templates invoked by user choice

NameDescription
build-raidcom-commandsTurn a storage task into validated raidcom commands.
explain-raidcom-commandExplain and check an existing raidcom command line.

Resources

Contextual data attached and managed by the client

NameDescription
raidcom conventionsLogin, instances, serial numbers, asynchronous commands, resource locking.
Minimal HORCM configurationWhat the host that runs raidcom needs.
Command listEvery raidcom command in the catalogue with its one-line summary.

TDQS

A4.1/5.0

Scored across 8 tools

Disambiguation4/5

The three "build" tools (build_command, build_script, build_recipe) share a surface but are clearly delineated by scope: one command, many commands, or a prebuilt workflow, and the descriptions explicitly cross-reference each other. Discovery (list_commands), documentation (describe_command), and validation (check_command) each have distinct roles, leaving only mild build_script-vs-build_recipe overlap.

Naming Consistency4/5

All eight tools use a uniform raidcom_ prefix, snake_case, and verb-first style (build_, list_, describe_, check_). The only deviation is raidcom_model_limits, which is noun-based rather than verb_noun, but it remains readable and unambiguous.

Tool Count5/5

Eight tools is a well-scoped set for an offline raidcom command builder, and each tool earns its place: discovery, docs, single build, multi-step build, recipe listing, recipe build, validation, and model limits. No obvious padding or redundancy.

Completeness4/5

The lifecycle is well covered from discovery through description, validation, single-command build, multi-step scripts, and recipes, with no execution by design. Minor gaps remain, such as a tool to interpret raidcom error codes or the asynchronous command_status output the generated scripts rely on.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues