Skip to main content
Glama
Sign In
mcp-zabbix

mcp-zabbix

by daedalus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

zabbix_hostgroup_delete

Delete host groups from Zabbix to remove unused monitoring scopes and simplify configuration.

Instructions

Zabbix API hostgroup.delete method

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

Input Schema

NameRequiredDescriptionDefault
paramsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It does not mention that this is a destructive operation, what side effects occur (e.g., if the hostgroup has hosts), required permissions, or error conditions. The name implies deletion, but the description fails to explicitly inform the agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short (one sentence), but it lacks structure and essential details. While it is concise, it sacrifices completeness to the point where it is not helpful. Front-loading is minimal, and every additional sentence could add value.

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

Completeness2/5

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

Given that this is a delete operation with no annotations and an undocumented parameter, the description is insufficient. It does not explain return values (even though an output schema exists, it is not described), error handling, or prerequisites. The tool is a minor wrapper, but as an interface for an AI agent, it fails to provide necessary context.

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

Parameters1/5

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

The input schema contains a single 'params' parameter with no description, and the tool description does not explain what properties this object should have (e.g., hostgroupid). Schema coverage is 0%, and the description adds no meaning. The parameter is effectively undocumented.

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

Purpose3/5

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

The description states it is the Zabbix API hostgroup.delete method, indicating the action (delete) and resource (hostgroup). However, it does not add any additional context beyond what the name already conveys, and it does not explicitly distinguish from sibling hostgroup tools beyond the method name.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. There is no discussion of prerequisites, when not to use it, or how it compares to other hostgroup-related tools like hostgroup_get or hostgroup_update.

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