Skip to main content
Glama
AliKarami

MikroMCP

by AliKarami
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Manage Address List Entry

manage_address_list_entry
DestructiveIdempotent

Add or remove firewall address list entries by IP or CIDR. Preview changes with dry-run mode, and keep operations idempotent by list and address.

Instructions

Add or remove a firewall address list entry. Idempotent by list name + address. Supports dry-run mode.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listYesAddress list name
actionYesAction to perform
dryRunNoPreview changes without applying.
addressYesIP address or CIDR to add/remove
commentNoOptional comment for the entry
timeoutNoExpiry timeout (e.g. 1d, 2h30m) — omit for permanent
routerIdNoRouter ID; omit to use the default router.
confirmationTokenNoToken from a prior APPROVAL_REQUIRED response. Re-submit the identical call with this token to confirm the destructive action.

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."
    • changedInput schema / required
      Previous value: -[
-  "routerId",
-  "action",
-  "list",
-  "address"
-]New value: +[
+  "action",
+  "list",
+  "address"
+]
  3. Addedv1.5.0
  4. Removedv1.1.0
  5. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations indicate destructiveHint=true and idempotentHint=true. Description reinforces idempotency and adds dry-run capability, providing useful behavioral context beyond annotations.

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?

Extremely concise: two sentences with no redundant information. Front-loaded with the core purpose, then key extras.

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

Completeness4/5

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

Covers essential aspects: operation, idempotency, dry-run. Does not explain return values (no output schema) or confirmation token logic in detail, but schema handles that. Adequate for a management tool with annotations.

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 coverage is 100% so baseline is 3. Description mentions idempotency by list+address, which adds meaning to list and address parameters, but overall adds limited new parameter-level insight beyond schema.

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

Purpose5/5

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

Description clearly states verb (add/remove) and resource (firewall address list entry). It distinguishes from sibling list_address_list_entries and mentions key features (idempotency, dry-run).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description implies usage for adding/removing entries but does not explicitly state when to use vs alternatives or when not to use. No when-not-to or alternative tool names are provided.

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