Skip to main content
Glama
Sign In
mcp-zabbix

mcp-zabbix

by daedalus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

zabbix_service_create

Create a new service in Zabbix using the service.create API method to define service structures for monitoring.

Instructions

Zabbix API service.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_service_create"
  }
}

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
Behavior1/5

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

No annotations are provided, and the description does not disclose any behavioral traits such as side effects (e.g., creating a service), required authentication, or return value structure. The agent has no information beyond the fact that it calls the create method, which is a serious omission.

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 only one sentence, which is too brief to convey meaningful information. It is not concise in a helpful way; under-specification makes it useless for an agent. A longer description with structured guidance would be necessary.

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 Zabbix service creation (likely requiring multiple fields like name, status, etc.), the description is completely inadequate. It fails to mention required parameters, behavior, or how the returned output confirms success.

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' property with no type constraints or descriptions (schema description coverage 0%). The description does not provide any parameter documentation, leaving the agent completely in the dark about what fields or structure the 'params' object should contain.

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 explicitly states the tool corresponds to the 'Zabbix API service.create method', clearly identifying the verb (create) and resource (service). This distinguishes it from sibling tools like service_get or service_delete. However, no additional context about what a service is in Zabbix is provided, leaving some ambiguity for unfamiliar agents.

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?

There are no guidelines on when to use this tool versus alternatives. With many sibling tools covering various operations on services, the lack of any usage context forces the agent to rely solely on the tool name for selection, which is insufficient.

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