Skip to main content
Glama

Add an iLO or OneView to the inventory

add_server

Adds an iLO or OneView to inventory through chat pop-ups, validates login via a secure password page, then makes the server available to tools immediately.

Instructions

Add one iLO or OneView to the user's inventory with pop-ups in the chat: a form for the type, address, name and user name, then a secure page for the password. The login is checked before anything is saved. The tools use the new server immediately. Call it when the user wants to add a server, or when no iLO or OneView is configured. Never ask for the password in chat, and never pass one; the secure page collects it.

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

Input Schema

NameRequiredDescriptionDefault
hostNoPre-fills the pop-up: IP address or name of the iLO or OneView.
nameNoPre-fills the pop-up: short name for the server.
typeNoPre-fills the pop-up: ilo or oneview.
usernameNoPre-fills the pop-up: user name (default Administrator).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare non-read-only, open-world, non-idempotent, non-destructive. The description adds substantial behavior: the call is interactive, opening a form pop-up then a separate secure password page, the credential is validated before anything is persisted, and the added server becomes immediately usable by other tools. Those are exactly the traits an agent cannot infer from the annotation block.

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?

Front-loaded with the action, then the interaction sequence, then the trigger conditions and the password rule. Slightly repetitive in the closing sentence ('Never ask for the password in chat, and never pass one; the secure page collects it'), but every clause carries actionable content.

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?

An output schema exists, so return values need no explanation. For a tool whose invocation triggers a two-step UI flow with a credential check, the description covers the sequence, the validation gate, and the post-add effect — everything needed to call it correctly without surprising the user.

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 coverage is 100% and each parameter already documents that it pre-fills the pop-up, so the description adds little new per-parameter meaning. Its one contribution is confirming the values are optional pre-fills rather than the actual submission payload, consistent with the zero-required-parameter schema. Baseline 3 applies.

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 plus a scope constraint: 'Add one iLO or OneView to the user's inventory.' The emphasis on 'one' implicitly separates it from bulk siblings like import_inventory, and the type restriction (iLO or OneView only) tells an agent exactly what is and is not in scope.

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

Usage Guidelines4/5

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

Gives explicit triggers: 'when the user wants to add a server, or when no iLO or OneView is configured.' It also states a hard interaction rule (never solicit or pass a password in chat). It stops short of naming a bulk alternative such as import_inventory for multi-server cases, so routing for fleets is left to inference.

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