Skip to main content
Glama
Sign In
Itential MCP Server

Itential MCP Server

Official
by itential
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Inventories

get_inventories
Read-onlyIdempotent

Retrieve all network device inventories from Itential Platform to manage groups for configuration, compliance, and automation tasks.

Instructions

Get all inventories from Itential Platform.

Inventories are collections of network devices organized for bulk configuration management, compliance checking, and automation tasks. They provide an organizational structure for grouping devices by function, location, or type.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYesResponse model for retrieving all inventories from Itential Platform. This model wraps a list of InventoryElement objects, providing a complete listing of all inventories configured on the platform instance along with their metadata.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and idempotentHint=true. The description adds no behavioral traits beyond this, such as pagination or response handling; it only adds domain context about inventories, which is not behavioral.

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?

Three concise sentences with the operation front-loaded. The conceptual explanation of inventories is useful but slightly extraneous; nonetheless, it is brief and doesn't waste words.

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?

For a parameterless list-all operation with an output schema present, the description is sufficient. It clearly defines the resource and scope; remaining details like return format are covered by the output schema.

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 tool has zero parameters and the schema is empty (100% coverage), so there is no parameter burden. The baseline of 4 applies; the description adds context about the inventory concept but no parameter-level details are needed.

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?

The description clearly states 'Get all inventories from Itential Platform' with a specific verb, resource, and 'all' scope. It distinguishes from sibling tools like describe_inventory by emphasizing the full collection, though it doesn't explicitly name an alternative.

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

Usage Guidelines3/5

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

The description implies the tool is for retrieving the complete inventory list and gives useful domain context about what inventories are. However, it provides no explicit when/when-not guidance and doesn't mention alternatives like describe_inventory for a single inventory.

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

Deploy Server

Other Tools