Skip to main content
Glama

add_dns_static

Add a static DNS entry to MikroTik RouterOS for mapping names to IP addresses, CNAMEs, MX, or SRV records, including optional TTL and comments.

Instructions

Adds a static DNS entry.

Notes: regexp: a regular expression the name must match. A regexp entry has no name, so name is ignored when regexp is given (RouterOS refuses both: "only name or regexp allowed").

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": {
      "name": "<name>"
    },
    "name": "add_dns_static"
  }
}

Input Schema

NameRequiredDescriptionDefault
ttlNo
nameYes
textNo
cnameNo
deviceNo
regexpNo
addressNo
commentNo
disabledNo
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

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful RouterOS-specific behavior: name and regexp are mutually exclusive and the server rejects both with a specific error. It says nothing about what happens on a duplicate name, whether creation requires permissions, or whether the entry is immediately active.

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?

The purpose sentence is front-loaded and the note is short, with no filler. The formatting is slightly rough (double backticks, an inline quoted server error), but nothing is redundant enough to warrant trimming.

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

Completeness2/5

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

For a 15-parameter mutation tool with zero schema description coverage, the description is far too thin; it documents one parameter interaction and nothing else. Return values are covered by the output schema, so that omission is acceptable, but the input side is largely unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 15 parameters, so the description must carry the load, yet it explains only the name/regexp interaction. Meaning for ttl, text, cname, address, mx_exchange, srv_target, device, and the rest is left entirely undocumented, and even the explained interaction does not say that regexp entries use 'text' for the replacement string.

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

Purpose4/5

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

The description opens with a specific verb and resource: 'Adds a static DNS entry,' which is immediately distinguishable from list/get/remove/update siblings. It does not, however, differentiate itself from the 'add_dns_regexp' sibling even though it accepts a regexp argument, so an agent must infer the boundary itself.

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?

There is no statement of when to use this tool versus 'add_dns_regexp' or 'update_dns_static', and no prerequisites or idempotency guidance. The only guidance present is an invocation constraint (name is ignored when regexp is given), which is a parameter rule rather than a when-to-use rule.

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