Skip to main content
Glama

add_dns_regexp

Adds a DNS regexp entry on a MikroTik device, mapping matching domain patterns to a specified IP address with optional TTL, comment, and disabled state.

Instructions

Adds a DNS regexp 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": {
      "regexp": "<regexp>",
      "address": "<address>"
    },
    "name": "add_dns_regexp"
  }
}

Input Schema

NameRequiredDescriptionDefault
ttlNo1d
deviceNo
regexpYes
addressYes
commentNo
disabledNo

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.2/5.0
Behavior2/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 mutation and safety profile is covered structurally. The description adds nothing beyond that—no note on whether duplicate regexps error out (relevant given idempotentHint=false), whether the entry takes effect immediately, or what device scoping means.

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?

It is a single, front-loaded sentence with no filler, which is structurally clean. But the brevity comes from omission rather than efficiency—there is no useful content to be concise about.

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?

A six-parameter mutation tool with zero schema descriptions needs the description to explain required regexp/address pairing and optional ttl/comment/disabled/device. An output schema exists so return values needn't be covered, but the input side is entirely unexplained.

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 six parameters, so the description carries the full burden and fails: it never mentions regexp, address, ttl, comment, disabled, or device. Only the word "regexp" in the name hints at one parameter, leaving five undocumented in both places.

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 states a specific verb+resource ("Adds a DNS regexp entry"), which is clearer than a tautology but does nothing to distinguish it from the sibling add_dns_static or any other add_* tool. An agent knows roughly what it creates but not how it differs from the static-DNS alternative.

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 add_dns_static as the alternative for ordinary static entries, and no prerequisite or scope statement. The agent must infer the choice between regexp and static DNS entries entirely on its own.

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