Skip to main content
Glama

set_dns_servers

Configures DNS servers on a MikroTik device, including DoH, cache size, TTL, and query limits for managing router DNS resolution.

Instructions

Sets DNS server configuration.

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

Input Schema

NameRequiredDescriptionDefault
deviceNo
serversYes
use_dohNo
cache_sizeNo
doh_serverNo
cache_max_ttlNo
verify_doh_certNo
max_udp_packet_sizeNo
allow_remote_requestsNo
max_concurrent_queriesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.29.6
    • addedInput schema / properties / allow_remote_requests / anyOf
      Added value: +[
      +  {
      +    "type": "boolean"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / allow_remote_requests / default
      Previous value: -falseNew value: +null
    • removedInput schema / properties / allow_remote_requests / type
      Removed value: -"boolean"
  2. Changed1 schema field changedv0.14.5
    • addedInput schema / properties / device
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Device"
      +}
  3. First observedv0.0.0

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare this is not read-only and not idempotent, so the safety profile is partially covered. The description adds nothing about what mutation actually occurs — notably whether the servers array replaces or appends to the existing server list, what the DoH and cache options do, or whether changes persist without an explicit commit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is tight and front-loaded with no wasted words, but its brevity stems from under-specification rather than economy — there is no structure to help an agent scan for mutation semantics or parameter guidance.

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?

For a 10-parameter mutation tool with no annotation detail on destructive/replacement semantics and zero schema descriptions, the description should carry substantial weight but instead carries none. The existing output schema excuses it from explaining return values, but that does not offset the missing mutation and parameter context.

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 10 parameters, and the description mentions only the generic notion of "DNS servers" without touching any of the nine optional arguments (use_doh, doh_server, verify_doh_cert, cache_size, cache_max_ttl, max_udp_packet_size, allow_remote_requests, max_concurrent_queries, device). It therefore adds no meaning beyond the bare parameter names.

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

Purpose3/5

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

The description gives a verb plus resource ("Sets" + "DNS server configuration"), which is enough to place it as the DNS write path alongside siblings like get_dns_settings and flush_dns_cache. However, "configuration" is broad and the sentence largely restates the name set_dns_servers; it does not say which aspects of DNS server setup are being changed versus left untouched.

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 when-to-use guidance, no mention of prerequisites (device targeting, admin access), and no routing to alternatives such as get_dns_settings for reading the current config or flush_dns_cache. The agent must infer usage purely from the tool name.

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