Skip to main content
Glama
Sign In
Raidcom MCP

Raidcom MCP

by visubramaniam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Find raidcom commands

raidcom_list_commands
Read-onlyIdempotent

Find the raidcom command for a storage task by describing your goal in plain words, or list available objects and actions when the exact command name is unknown.

Instructions

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "raidcom_list_commands"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results for a query (default 10).
queryNoWhat you want to do, in plain words.
actionNoOnly this action: add, delete, get, modify, extend, initialize, set, reset, ...
objectNoOnly this object: ldev, lun, host_grp, hba_wwn, pool, dp_pool, port, parity_grp, ...

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.8

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to disclose mode behavior — and it does: the no-arg call dumps every object with its actions, the query mode ranks matches and reports a confidence rating for the top hit. It stops short of describing result shape or what a low confidence score implies for follow-up, which is the remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Six short sentences, front-loaded with the trigger condition, then the three modes in the order an agent would try them, then the handoff. The quoted query examples are illustrative rather than padding, and no sentence restates the tool name or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-required-parameter discovery tool with no output schema, the description covers every invocation path (empty, query, action/object, limit-via-schema) and tells the agent where to go next in the toolchain. Nothing needed to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all four parameters are already documented, and the description adds only the query-phrasing examples ('map a volume to a host group') plus the action/object intersection rule. The `limit` parameter and its default of 10 are left entirely to the schema. Baseline 3 applies when the schema carries the weight.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Find raidcom commands') and then enumerates the three distinct modes of operation (no args = full catalog, `query` = ranked fuzzy match, `action`/`object` = exact filter). It explicitly routes to siblings raidcom_describe_command and raidcom_build_command, so an agent can separate it from them without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ('Use this first when you do not know the exact command name') and a clear handoff path: describe_command next, or build_command 'if you already know the options.' Both the when-to-use and the when-to-use-something-else cases are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools