Skip to main content
Glama

Import servers from a file

import_inventory

Imports multiple iLO and OneView entries from an .ini or .csv file; the user selects the file, confirms detected entries, and supplies one shared password for entries lacking credentials.

Instructions

Import many iLO and OneView entries from a .ini or .csv file (Excel: save as CSV) with pop-ups in the chat: the user types the file's path, confirms what was found, and gives one shared password on a secure page for entries that have none. Optionally checks each login. The tools use the entries immediately. Takes no arguments: the user chooses the file, not you.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare the safety profile (not read-only, open-world, non-idempotent, non-destructive). The description adds the actual interaction model: chat pop-ups, user-supplied path, a confirmation of discovered entries, a shared password collected on a secure page for entries lacking one, optional per-entry login checks, and immediate use of imported entries. That is substantial behavior beyond the structured fields.

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?

Four compact sentences, front-loaded with the core action and file formats, then the interaction flow, then the crucial no-arguments constraint. No filler; each sentence contributes a distinct fact.

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

Completeness4/5

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

Covers the full user-interaction flow and credential handling for an additive import tool, and an output schema exists to explain returns. It stops short of stating what happens on duplicate or conflicting entries and how failures mid-import are reported, which would matter for a non-idempotent bulk write.

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?

The schema has zero parameters, so the baseline is 4. The description reinforces the empty signature by explaining why (the user, not the agent, selects the file), which adds useful meaning to the parameterless contract.

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

Purpose4/5

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

States a specific verb and resource ('Import many iLO and OneView entries') plus supported file formats (.ini/.csv), which clearly separates it from single-entry tools like add_server. It never names a sibling explicitly, so differentiation is inferential rather than explicit.

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 strong invocation guidance: 'Takes no arguments: the user chooses the file, not you,' which prevents an agent from fabricating a path. The 'import many' framing implies use over add_server for bulk loads, but no alternative is named and no when-not condition is given.

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