Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

by mhajder

Proxy Create

proxy_create

Create a Zabbix proxy to collect monitoring data from remote or firewall-separated networks and report it to the central server. Set active or passive mode and add an optional description.

Instructions

Create a new proxy in Zabbix.

Proxies allow distributed monitoring by collecting data from remote networks and reporting to the central Zabbix server. Useful for firewall-separated networks or high-latency connections.

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

Input Schema

NameRequiredDescriptionDefault
nameYesProxy name.
descriptionNoOptional description explaining the proxy's purpose or location.
operating_modeNo0=active, 1=passive.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.3

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare a non-readonly, non-idempotent, non-destructive write, so the agent knows this mutates state. The description adds domain background about distributed monitoring but nothing beyond annotations about failure modes (duplicate name, auth requirements, TLS setup) or what is returned, which are the details a create call actually needs.

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

Conciseness4/5

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

The action statement is front-loaded in the first line and the second paragraph is short explanatory context rather than filler. It is slightly verbose for a three-parameter create tool, but nothing is redundant.

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

Completeness4/5

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

An output schema exists, so return values need not be explained, and all three parameters are documented, leaving the description to establish what a proxy is and why one would create it – which it does. The only real gap is post-creation behavior on naming conflicts or permissions.

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?

Schema description coverage is 100%, with name, optional description, and operating_mode (0=active, 1=passive) all documented in the schema. The description adds no formatting, defaults, or semantics beyond what the schema already states, so the baseline of 3 applies.

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?

States a specific verb and resource ('Create a new proxy in Zabbix') and follows with what a proxy is for, so the object is unambiguous. It does not explicitly contrast with the sibling proxy_get/proxy_update/proxy_delete, relying on the name to do that routing work.

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

Usage Guidelines3/5

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

The second paragraph gives a use case ('firewall-separated networks or high-latency connections'), which hints at when this capability matters, but it never says when to choose this tool over proxy_update, proxy_get, or configuration_import, nor any prerequisites such as required permissions or name uniqueness.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.