Skip to main content
Glama
Sign In

DZPage DayZ Tools

by com.dzpage
OverviewDiscussionsAdmin

Explain a DayZ server setting

explain_server_setting
Read-onlyIdempotent

Explain one setting of a DayZ server's db/globals.xml (e.g. LootDamageMax, CleanupLifetimeDeadPlayer, ZombieMaxCount) or cfggameplay.json (e.g. staminaMax, disableBaseDamage, PlayerData.StaminaData.staminaMax): what it does, the vanilla value (per map for cfggameplay.json), the engine default where it differs, value type, unit, sensible range and options, a ready line for the file and a link to the matching dzpage.com editor. An unknown name returns the closest setting names.

Input Schema

NameRequiredDescriptionDefault
mapNocfggameplay.json only: vanilla value of this map instead of all maps
langNoLanguage for names, descriptions and linksen
settingYesVariable name from globals.xml, or key or path from cfggameplay.json

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / map / description
      Previous value: -"cfggameplay.json only: vanilla value of this map instead of all three"New value: +"cfggameplay.json only: vanilla value of this map instead of all maps"
    • changedInput schema / properties / map / enum
      Previous value: -[
-  "chernarus",
-  "livonia",
-  "sakhal"
-]New value: +[
+  "chernarus",
+  "livonia",
+  "sakhal",
+  "nasdara"
+]
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare the safe read-only, idempotent profile. The description adds meaningful behavior beyond them: the fallback that an unknown name returns the closest matching setting names, plus a detailed account of what is returned (vanilla value, engine default, type, unit, range, ready file line, editor link).

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?

It is one dense sentence but front-loads the core action ('Explain one setting...') before enumerating return content, so the key intent is immediately clear. Slightly run-on, but every clause carries information.

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

Completeness5/5

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

With no output schema, the description takes on the burden of describing return values and does so thoroughly, covering both source files, per-map variance, engine defaults, and the unknown-name edge case. An agent has everything needed to call it correctly.

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%, so parameters are already documented. The description adds examples of valid setting names and notes that cfggameplay.json values are per-map, reinforcing the map parameter, but adds no syntax beyond the schema.

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

Purpose5/5

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

States a specific verb (Explain) and resource (one DayZ server setting), scoping it to db/globals.xml and cfggameplay.json with concrete examples. This clearly distinguishes it from siblings like validate_config_file and analyze_server_log.

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

Usage Guidelines4/5

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

The description gives clear context for use — looking up a single named setting and its metadata — with example names. It does not explicitly name when-not-to-use or point to an alternative such as validate_config_file, so it stops short of full routing guidance.

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

All DZPage DayZ Tools toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources