mcp-zabbix

by daedalus

Overview Schema Source Related Servers Discussions Admin

Python

Remote

zabbix_graphprototype_delete

Delete graph prototypes in Zabbix. Removes specified graph prototypes from monitoring templates.

Instructions

Zabbix API graphprototype.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_graphprototype_delete"
  }
}

Input Schema

Name	Required	Description	Default
`params`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Apr 18, 2026

TDQS

D1.3/5.0

Behavior1/5

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

No annotations exist. The description fails to disclose any behavioral traits such as idempotency, side effects, authentication requirements, or error behavior. 'Delete' implies mutation but offers no 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 short sentence but it is under-specified and fails to convey useful information. It is concise but not effective.

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?

Even with an output schema present, the description omits any explanation of the tool's purpose, behavior, or return values. It is completely inadequate for a deletion operation.

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 a single 'params' field with no constraints (additionalProperties true). The description adds no meaning about what parameters are expected, despite 0% schema description coverage.

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 restates the method name ('graphprototype.delete') and mentions Zabbix API, but does not clearly define what a graph prototype is or that it deletes a specific resource. It is a tautology.

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 on when to use this tool versus alternatives like 'zabbix_graphprototype_get' or 'zabbix_graphprototype_create'. No prerequisites, context, or exclusions provided.

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

Deploy Server