Skip to main content
Glama

disable_route

Idempotent

Deactivate a MikroTik route by route ID to stop traffic from using it. Use when a route must be temporarily taken out of service.

Instructions

Disables a route.

Notes: route_id: "*N" or "N" from list output e.g. "*3"

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": "disable_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNo
route_idYes

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

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, so the agent knows the operation is a reversible, repeatable state change; the description adds no behavior beyond that. It does not say whether the route stays in configuration, what happens to traffic using it, or whether re-enabling restores prior state.

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 purpose sentence is front-loaded and the whole definition is two short lines with no filler. The indented "Notes:" block is slightly awkward formatting but nothing is wasted.

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 no explanation, but the definition still omits the meaning of `device`, any alternative-selection guidance among the many sibling disable_*/remove_route tools, and confirmation of reversibility. For a mutation tool with 0% schema coverage this is thin.

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%, so the description must compensate. It does explain the critical route_id format ("*N" or "N" as shown in list output, e.g. "*3"), which is genuinely useful, but the `device` parameter is left completely unexplained.

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?

"Disables a route" states a specific verb and resource, which clearly separates it from remove_route or update_route by implication. It does not explicitly name or contrast any sibling (e.g. enable_route), so it stops short of a 5.

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 guidance on when to disable versus remove or update a route, and no stated prerequisites such as the route needing to exist or be currently enabled. The notes explain the route_id format, which is parameter help rather than usage routing.

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