Skip to main content
Glama
Sign In
Itential MCP Server

Itential MCP Server

Official
by itential
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Delete Inventory

delete_inventory
Destructive

Permanently remove an inventory grouping and its device associations from Itential Platform; devices remain untouched.

Instructions

Delete an inventory from Itential Platform.

Permanently removes an inventory and all its device associations. The devices themselves are not affected; only the inventory grouping is deleted. This operation cannot be undone.

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": {
      "name": "<name>"
    },
    "name": "delete_inventory"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe name of the inventory to delete

Output Schema

NameRequiredDescriptionDefault
statusYesStatus of the delete operation
messageYesShort description of the status of the operation

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

The description adds significant behavioral context beyond the annotations: it states the operation permanently removes the inventory and all device associations, clarifies that devices themselves are not affected, and warns that the operation cannot be undone. This aligns with and expands upon the destructiveHint annotation, providing users with a clear understanding of side effects.

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?

The description is concise and front-loaded with the primary action, followed by essential caveats. Every sentence adds value: scope, side effects on devices, and irreversibility. No redundant or extraneous information is present.

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?

For a simple tool with one parameter, a clear schema, and relevant annotations, the description fully covers the necessary context. It explains the operation's scope, side effects, and irreversibility, which is sufficient for an agent to decide when and how to invoke the tool.

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?

The input schema already provides 100% coverage with a clear description for the single 'name' parameter. The tool description does not add any additional parameter semantics, so the baseline score of 3 is appropriate.

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?

The description clearly states the action ('Delete an inventory') and the resource ('inventory from Itential Platform'), and it distinguishes itself from sibling tools like create_inventory and describe_inventory. It also clarifies the scope of deletion (inventory grouping and device associations) versus what remains unaffected (devices).

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?

The description clearly indicates this tool is for permanent deletion, providing context that it cannot be undone. However, it does not explicitly mention alternatives or when not to use it, such as suggesting describe_inventory for informational purposes. The context is clear but lacks explicit exclusions.

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