Skip to main content
Glama

Oneview List Server Profiles

oneview_list_server_profiles
Read-onlyIdempotent

Lists HPE OneView server profiles with status, assigned hardware, template compliance, firmware baseline, boot mode, and connection count to audit profile configuration and compliance.

Instructions

Server profiles: status, assigned server hardware, template and compliance, firmware baseline, boot mode and connection count.

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

Input Schema

NameRequiredDescriptionDefault
applianceNoOneView appliance 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.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds that results carry compliance, firmware baseline, boot mode and connection count, which is useful content signaling but arguably duplicates the output schema; it says nothing about pagination, filtering, or failure behavior when the appliance is unreachable.

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

Conciseness4/5

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

A single compact multi-item fragment with no filler. It is efficient, though the lack of a leading verb makes it read like a schema excerpt rather than an instruction.

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?

With an output schema, rich annotations and one fully documented optional parameter, the definition is serviceable but leaves the caller uncertain about cross-appliance scope and result size. The output schema carries the return-value burden, so this gap is moderate rather than severe.

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?

Only one optional parameter exists and the schema documents it at 100% coverage, including the default and the instruction to omit it to use the first appliance. The description adds no meaning beyond that, which is the expected baseline when the schema does the explaining.

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 text is a noun-phrase field list rather than a statement of action: 'Server profiles: status, assigned server hardware, template and compliance...'. The tool name supplies the verb 'list', and the enumeration of returned attributes goes slightly beyond the name, but it does not distinguish this tool from oneview_list_server_hardware or explain scope (one appliance vs. fleet).

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 exclusions, and no mention of sibling tools such as oneview_list_server_hardware or oneview_get_server_hardware that an agent must choose between. An agent must infer selection purely from tool names.

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