Skip to main content
Glama
Sign In
mcp-zabbix

mcp-zabbix

by daedalus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

zabbix_authentication_exists

Verify user authentication status in Zabbix. Returns boolean indicating if credentials are valid.

Instructions

Zabbix API authentication.exists 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_authentication_exists"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.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 behavioral traits such as whether the tool is read-only or mutating. The name implies a read operation, but this is not stated explicitly.

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 very short (5 words), but it is under-specification rather than effective conciseness. It does not efficiently convey essential information.

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 that there is an output schema and multiple sibling tools, the description should explain what the tool returns (e.g., a boolean) and how it differs from similar tools. It provides no context at all.

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 one parameter ('params') with no description coverage (0%). The description does not explain what 'params' should contain, leaving the agent without necessary information to invoke the tool correctly.

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

Purpose1/5

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

The description 'Zabbix API authentication.exists method' merely restates the tool name without specifying what it does (e.g., check if an authentication entity exists). It lacks a verb and resource, making the purpose unclear.

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 is given on when to use this tool versus siblings like zabbix_authentication_get or zabbix_authentication_create. There is no mention of prerequisites or context.

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