Skip to main content
Glama
Sign In
mcp-zabbix

mcp-zabbix

by daedalus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

zabbix_valuemap_create

Create a new value mapping in Zabbix to translate raw values into meaningful labels.

Instructions

Zabbix API valuemap.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_valuemap_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 carries full burden for behavioral disclosure, but it merely states the API method name. It does not mention side effects (e.g., creation of a new record), required permissions, or any consequences of using this tool.

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, but this is due to under-specification rather than conciseness. Every word should add value; here, the sentence adds no useful information beyond the tool name.

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 Zabbix valuemap creation tool, with no annotations, no parameter details, and no output schema description, the description is wholly inadequate. It fails to inform the agent about required inputs, behavior, or the returned data.

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 optional 'params' field with no description, and schema description coverage is 0%. The description adds no meaning to the parameter, leaving its structure and purpose entirely undefined.

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 valuemap.create method' essentially restates the tool name without clarifying what a valuemap is or how it differs from siblings. It does not specify the verb 'create' in the context of Zabbix beyond the name, making it 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 Guidelines2/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 like zabbix_valuemap_get or zabbix_valuemap_update. The description lacks any context about prerequisites, exclusions, or typical use cases.

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