Skip to main content
Glama
Sign In
mcp-zabbix

mcp-zabbix

by daedalus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

zabbix_iconmap_delete

Delete icon maps in Zabbix to remove unused or outdated mapping configurations.

Instructions

Zabbix API iconmap.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_iconmap_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.8/5.0
Behavior2/5

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

Without annotations, the description should disclose behavioral traits such as irreversibility, side effects, or required permissions. The description only states it is a 'delete method' without any such details.

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 a single sentence, but it is too brief to be useful. It sacrifices necessary detail for brevity, making it inadequate for effective tool selection and invocation.

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

Completeness1/5

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

Given the complexity of a delete operation and the lack of annotations, the description is severely incomplete. It fails to provide the agent with enough context to understand how to use the tool or interpret its effects.

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 has 0% coverage with a generic 'params' object. The description adds no information about what parameters are needed, leaving the agent without guidance on how to invoke the tool.

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 the verb ('delete') and resource ('iconmap'), making the basic purpose clear. However, it does not explain what an iconmap is or differentiate it from other delete tools in the sibling set, relying solely on the tool name.

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

Usage Guidelines1/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 (e.g., zabbix_iconmap_get for retrieval or zabbix_iconmap_create for creation). There is no mention of prerequisites or context for deletion.

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