Skip to main content
Glama
AliKarami

MikroMCP

by AliKarami
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Manage DNS Settings

manage_dns_settings
DestructiveIdempotent

Update DNS resolver settings such as upstream servers, cache size, TTL, and remote request handling. Idempotent operation avoids changes when nothing differs; dry-run preview available.

Instructions

Update DNS resolver settings (upstream servers, cache size, cache TTL, allow-remote-requests). Idempotent: returns no_change if nothing differs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dryRunNoPreview changes without applying.
serversNoComma-separated upstream DNS server IPs (e.g. '8.8.8.8,1.1.1.1')
routerIdNoRouter ID; omit to use the default router.
cacheSizeNoDNS cache size in KiB
cacheMaxTtlNoMaximum cache TTL (e.g. '1d', '00:30:00')
maxUdpPacketSizeNoMaximum UDP packet size in bytes
confirmationTokenNoToken from a prior APPROVAL_REQUIRED response. Re-submit the identical call with this token to confirm the destructive action.
allowRemoteRequestsNoAllow router to answer DNS queries from the network

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.8.0
    • addedInput schema / properties / confirmationToken
      Added value: +{
+  "description": "Token from a prior APPROVAL_REQUIRED response. Re-submit the identical call with this token to confirm the destructive action.",
+  "type": "string"
+}
  2. Changed3 schema fields changedv1.6.0
    • changedInput schema / properties / dryRun / description
      Previous value: -"Preview changes without applying"New value: +"Preview changes without applying."
    • changedInput schema / properties / routerId / description
      Previous value: -"Target router identifier from the router registry"New value: +"Router ID; omit to use the default router."
    • removedInput schema / required
      Removed value: -[
-  "routerId"
-]
  3. Addedv1.5.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations provide idempotentHint=true and destructiveHint=true. The description adds context by explaining idempotency ('returns no_change if nothing differs') and listing what settings are updated. However, it doesn't elaborate on authorization needs, side effects, or the destructive nature beyond the annotation.

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

Conciseness5/5

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

Two sentences, no wasted words. First sentence clearly states purpose and scope; second adds valuable idempotency behavior. Highly concise.

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

Completeness3/5

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

Given 8 parameters (all documented in schema), annotations, and no output schema, the description covers purpose and idempotency but lacks usage guidelines and behavioral details (e.g., confirmation token requirement, destructive action). Adequate but not comprehensive.

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

Parameters3/5

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

Schema description coverage is 100%, so baseline is 3. The description summarizes key parameters (upstream servers, cache size, cache TTL, allow-remote-requests) but does not add meaning beyond the schema. No additional parameter semantics provided.

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 clearly states the verb ('Update'), the resource ('DNS resolver settings'), and lists specific settings (upstream servers, cache size, cache TTL, allow-remote-requests). It distinguishes from siblings like 'get_dns_settings' by being a write operation, though not explicitly.

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?

No guidance on when to use vs alternatives. Does not mention when not to use, prerequisites, or context for choosing this tool over related tools like 'manage_dns_entry' or 'get_dns_settings'.

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