Skip to main content
Glama

update_dns_static

Idempotent

Updates an existing static DNS record on a MikroTik RouterOS device, allowing changes to address, CNAME, MX, SRV, TTL, or comments without recreating it.

Instructions

Updates a static DNS entry.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "entry_id": "<entry_id>"
    },
    "name": "update_dns_static"
  }
}

Input Schema

NameRequiredDescriptionDefault
ttlNo
nameNo
textNo
cnameNo
deviceNo
regexpNo
addressNo
commentNo
disabledNo
entry_idYes
srv_portNo
srv_targetNo
srv_weightNo
mx_exchangeNo
srv_priorityNo
mx_preferenceNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.14.5
    • addedInput schema / properties / device
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Device"
      +}
  2. First observedv0.0.0

TDQS

D1.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds nothing on top of that: no mention of partial-update semantics (all non-required fields default to null), whether omitted fields are preserved, or what identification by entry_id requires.

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 single sentence is technically efficient with no wasted words, but it is under-specification rather than conciseness. There is no structure to front-load because there is no substantive content.

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?

This is a mutation tool with 16 sparse, undocumented parameters including mutually exclusive DNS record fields, and the description says nothing about them. An output schema exists, so return values need not be explained, but that does not offset the total absence of parameter and update-semantics guidance.

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?

Schema description coverage is 0% across 16 parameters, and the description compensates for none of it. Cryptic field names such as `text`, `regexp`, `srv_target`, `srv_weight`, and `mx_exchange` are left completely unexplained, so an agent cannot tell which record type each applies to or that null defaults mean unchanged.

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 sentence "Updates a static DNS entry" restates the tool name and title almost verbatim without adding scope or mechanics. A reader learns nothing beyond what `update_dns_static` already implies, and no distinction is drawn from siblings such as `enable_dns_static` or `disable_dns_static`.

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 when-to-use guidance, no prerequisites, and no alternatives are named. Whether to reach for this versus `add_dns_static` or the enable/disable siblings is left entirely to inference from names.

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