Skip to main content
Glama

update_route

Idempotent

Modify an existing MikroTik route by ID to change its gateway, destination, distance, routing table, VRF, or disabled state. Use it to correct or adjust routing behavior on a RouterOS device.

Instructions

Updates a route.

Notes: route_id: "*N" or "N" from list output e.g. "*3" dst_address: CIDR e.g. "192.168.1.0/24" check_gateway: "ping" or "arp" distance: 1-255 routing_table: name of a table from /routing table; "" moves the route back to "main", since every RouterOS 7 route belongs to a table. Pass "" to vrf_interface or pref_src to clear them.

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": {
      "route_id": "<route_id>"
    },
    "name": "update_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeNo
deviceNo
commentNo
gatewayNo
disabledNo
distanceNo
pref_srcNo
route_idYes
dst_addressNo
target_scopeNo
check_gatewayNo
routing_tableNo
vrf_interfaceNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.19.4
    • removedInput schema / properties / routing_mark
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "title": "Routing Mark"
      -}
    • addedInput schema / properties / routing_table
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Routing Table"
      +}
  2. Changed1 schema field changedv0.14.5
    • addedInput schema / properties / device
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Device"
      +}
  3. First observedv0.0.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare it as a non-read-only, idempotent, non-destructive, closed-world update, so safety is covered. The description adds genuinely non-obvious behavior — empty string clears vrf_interface/pref_src and "" in routing_table moves the route back to "main" — which is valuable. However, it never states whether an omitted (null) parameter leaves a field unchanged or clears it, a critical ambiguity for an update tool.

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?

A one-line purpose followed by a compact per-parameter notes list is well front-loaded and free of filler. The per-field notes are scannable, though the routing_table entry runs across two lines and mixes format with side-effect behavior.

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?

With 13 parameters, 0% schema coverage, and no annotations beyond safety hints, the description should define more of the surface; six parameters have no documented meaning at all. The null-versus-empty-string distinction is decisive for a partial-update tool and is only half-addressed. An output schema exists, so return values correctly need not be explained.

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 0% across 13 parameters, so the description must compensate, and it does partially: it documents formats for route_id, dst_address, check_gateway, distance, routing_table, and clearing semantics for vrf_interface and pref_src. It says nothing about gateway, disabled, comment, device, scope, or target_scope, leaving roughly half the parameters with no meaning anywhere.

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?

States a specific verb and resource ("Updates a route"), and the notes make clear it operates on an existing RouterOS 7 route identified by route_id from list output. It does not explicitly distinguish itself from add_route or remove_route, but the CRUD verb makes the intent unambiguous.

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 explicit when-to-use or when-not guidance, and no mention of alternatives such as add_route for creating a route or remove_route for deleting one. The only implied usage context is that route_id comes from list output, which hints at a prerequisite lookup but is not framed as guidance.

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