Skip to main content
Glama

Com List Groups

com_list_groups
Read-onlyIdempotent

Lists COM server groups with member serials, firmware and iLO compliance status, and whether firmware updates automatically when servers are added.

Instructions

COM server groups: members (serials), compliance (firmware, iLO settings) and whether firmware is updated automatically when a server is added.

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": "com_list_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoCOM account name from list_servers; omit to use the first one.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered structurally. The description adds only a static list of what a group contains, which is output-shape information rather than behavior, and says nothing about pagination, scoping, or how an empty group list is handled.

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

Conciseness3/5

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

The text is short and free of filler, but it is a single unpunctuated fragment rather than a front-loaded statement of the action. Brevity here reflects under-specification as much as conciseness.

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

Completeness3/5

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

An output schema exists, so return values need not be described, and annotations cover the read-only semantics. What remains missing is the core action statement — that this lists the groups for a given account — which is the minimum an agent needs before invoking a list tool.

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?

With one parameter at 100% schema description coverage, the schema already explains the account input and its default. The description contributes no additional parameter meaning, so the baseline of 3 applies.

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

Purpose3/5

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

The description names the resource (COM server groups) and enumerates its facets — members/serials, compliance, and auto-update behavior — but never uses an action verb like 'list' or 'retrieve', and it reads as a noun-phrase fragment. An agent can guess this enumerates groups, but it gets no explicit statement of the operation and no differentiation from siblings such as com_list_servers or list_servers.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no named alternative. The account parameter's default is documented only in the schema, so the description does nothing to route an agent between this tool and the other list_* tools.

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