Skip to main content
Glama

disable_dns_static

Idempotent

Disables a specified static DNS entry by entry ID on a MikroTik device, stopping that record from resolving without deleting it.

Instructions

Disables 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": "disable_dns_static"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNo
entry_idYes

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.6/5.0
Behavior2/5

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

Annotations already declare this is a non-read-only, idempotent, non-destructive, closed-world mutation. The description adds nothing beyond them: it doesn't say whether the entry is retained but deactivated, whether the change is reversible, or what state changes. With annotations carrying the safety profile the bar is lower, but the description contributes no extra behavioral context.

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?

One short, front-loaded sentence with no wasted wording, but the brevity reflects under-specification rather than tight editing — a clause about entry identification or device targeting would have earned its place.

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?

An output schema exists, so return values need not be described, and annotations cover reversibility of intent (non-destructive). However, for a two-parameter mutation tool with 0% schema coverage, the definition leaves critical gaps: the meaning of entry_id and the role of the device parameter are unaddressed.

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% for both parameters, so the description must compensate and does not. It never explains what entry_id refers to (internal id vs. name vs. address) or where to obtain it, and the optional 'device' parameter is left completely unaddressed even though it presumably selects which router to act on.

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 gives a specific verb and resource — 'Disables a static DNS entry' — which is unambiguous and implicitly distinguishes it from enable_dns_static and remove_dns_static. It does not explicitly name those siblings, so it stops short of a 5.

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 guidance on when to disable versus remove or update an entry, no stated preconditions (e.g., entry must exist / be enabled), and no mention of the inverse operation available via enable_dns_static. Usage is only inferable 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