Skip to main content
Glama

List Morpheus options

list_morpheus_options
Read-only

List the provisioning options an HPE Morpheus credential can reach: groups, clouds, networks, layouts, and service plans, each with the numeric id create_morpheus_cluster requires. Call this before create_morpheus_cluster to resolve group_id, cloud_id, network_id, layout_id, and the plan ids. Read-only; talks to the customer's Morpheus API, so it can take a few seconds.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "credential_id": "<credential_id>"
    },
    "name": "list_morpheus_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
credential_idYesUUID of the HPE Morpheus credential.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces this while adding genuinely new context: it hits the customer's Morpheus API and may take a few seconds. It does not cover pagination or failure modes, but the latency and external-dependency disclosure is valuable beyond the annotations.

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?

Two sentences, front-loaded with the resource and scope, then the sequencing instruction and latency note. No redundant restatement of the title or schema.

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?

With no output schema, the description carries the return-value burden and does so by naming the five option categories and the numeric ids they yield, which is exactly what an agent needs to chain into create_morpheus_cluster.

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

Parameters4/5

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

Schema coverage is 100% and the single credential_id is documented there, so the baseline is 3; the description adds that the credential scopes which options are reachable, giving the parameter meaning beyond its type.

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 ('List the provisioning options an HPE Morpheus credential can reach') and enumerates the returned categories (groups, clouds, networks, layouts, service plans), which distinguishes it from generic list_* siblings.

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?

Explicitly says to call it before create_morpheus_cluster and names the exact ids it resolves (group_id, cloud_id, network_id, layout_id, plan ids), so the when-to-use condition and the alternative are both unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.