Skip to main content
Glama
Sign In
mcp-zabbix

mcp-zabbix

by daedalus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

zabbix_drule_create

Create Zabbix discovery rules to automate host and service detection using the drule.create API method.

Instructions

Zabbix API drule.create 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_drule_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.5/5.0
Behavior1/5

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

With no annotations, the description must disclose behavioral traits. It only states the API method name, offering no information about side effects, permissions, or result behavior.

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 (5 words) but fails to provide essential information. Conciseness is not achieved when it sacrifices clarity and completeness.

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 creating a Zabbix discovery rule, the description is completely inadequate. It does not explain the tool's purpose beyond the method name, nor does it reference the output schema or any constraints.

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 description adds no meaning to the input schema. Schema coverage is 0%, and the single 'params' parameter is left entirely undocumented, leaving the agent with no guidance on required fields or structure.

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

Purpose2/5

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

The description 'Zabbix API drule.create method' vaguely indicates it creates a drule, but it lacks specificity about what a drule is and does not differentiate from sibling tools like zabbix_drule_update or zabbix_drule_delete.

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 on when to use this tool versus alternatives. The description provides no context such as prerequisites, typical use cases, or scenarios where drule_create is appropriate.

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