Skip to main content
Glama

flush_dns_cache

DestructiveIdempotent

Clears the DNS cache on a MikroTik RouterOS device to resolve stale or incorrect DNS lookups. Specify the target device to refresh name resolution data.

Instructions

Flushes the DNS cache.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "flush_dns_cache"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNo

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

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

Annotations already disclose the key traits (destructiveHint=true, idempotentHint=true, readOnlyHint=false, openWorldHint=false), so the description's burden is lighter, but it still adds nothing about what is actually lost — cached resolutions being dropped and short-term resolution latency — or whether the flush is local or device-wide. For a destructive operation, this silence leaves the agent without the operational context annotations cannot express.

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?

One short sentence with no waste, but it is under-specified rather than concise — it front-loads nothing beyond the title and leaves every decision-relevant detail out.

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, but for a destructive, idempotent cache-flush tool with an undocumented device selector, the definition is not complete enough to call correctly or safely.

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%, and the single `device` parameter (nullable, no enum, no description) is completely unexplained in the description. The agent cannot tell whether omitting it flushes the local cache or all devices, which materially changes the effect of a destructive call.

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?

"Flushes the DNS cache" restates the tool name flush_dns_cache almost verbatim, so the description is essentially a tautology. It does convey the verb and resource, but adds nothing about scope, target device, or how it differs from siblings like get_dns_cache or flush_route_cache.

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 prerequisites, and no mention of alternatives such as get_dns_cache for inspecting entries or get_dns_cache_statistics for diagnosing before flushing. The agent must infer the entire usage context from the name alone.

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