Skip to main content
Glama

add_blackhole_route

Adds a blackhole route to discard traffic for a specified CIDR destination on MikroTik RouterOS, with optional distance and comment.

Instructions

Adds a blackhole route.

Notes: dst_address: CIDR e.g. "10.0.0.0/8" distance: 1-255

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": {
      "dst_address": "<dst_address>"
    },
    "name": "add_blackhole_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNo
commentNo
distanceNo
dst_addressYes

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.8/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 safety profile is covered. The description adds nothing behavioral beyond that: it does not say that matching traffic is silently dropped, whether duplicate additions fail, or what the device parameter does when omitted. The two notes it supplies are parameter hints, not behavior.

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

Conciseness4/5

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

The description is two compact sentences with the core action front-loaded and no filler. The Notes block is slightly awkward in formatting but every line carries information.

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?

An output schema exists, so return values need not be explained, but with four parameters at 0% schema coverage and only thin annotations, the definition leaves too much for the agent to guess. It is minimally sufficient to invoke the tool but not sufficient to invoke it correctly in the presence of duplicate routes or multi-device setups.

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%, so the description must compensate and it only partly does: dst_address gets a CIDR example and distance gets a 1-255 range (though its meaning as route preference is never stated). The device and comment parameters are completely undocumented in both the schema and the description.

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?

"Adds a blackhole route" gives a specific verb and resource, so an agent knows this creates a discard route rather than a normal path. It does not distinguish itself from the sibling tools add_route and add_default_route, and it never explains what a blackhole route actually does with matching traffic.

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 at all: no mention of preferring this over add_route with an unreachable gateway, no prerequisite or permission notes, and no indication of what happens if a route for the same prefix already exists. The agent must infer usage entirely 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