Retrieve documentation links, read/write class, permission status, and usage tips for a Zabbix API method to plan safe calls.
Docs link, read/write class, permission status and usage tips for one API method.
| Name | Required | Description | Default |
|---|---|---|---|
| method | Yes | e.g. 'host.create' |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the read-only and non-destructive annotations, the description discloses the single-method scope and four types of information the lookup provides. This usefully frames it as metadata inspection, although lookup-failure behavior and whether permission status is user-specific remain unspecified.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact and front-loaded with both the returned information and the single-method scope. It contains no filler or redundant explanation.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter, read-only lookup with no output schema, listing the expected information provides enough context for basic selection and invocation. Explicit sibling routing and a little more detail about permission status would make it more complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the method parameter already includes the useful example 'host.create'. The description reinforces that only one method is described but adds no parameter syntax or validation details beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description identifies the resource as one API method and specifies the information supplied: a docs link, read/write class, permission status, and usage tips. It does not explicitly distinguish this inspection tool from zabbix_search_methods or zabbix_raw_api.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'for one API method' implies use when a specific method is already known and its documentation or permissions are needed. There is no explicit guidance to use zabbix_search_methods for method discovery or zabbix_raw_api for executing API calls.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.