Skip to main content
Glama
Kykyryky23

keenetic

by Kykyryky23
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Привязать маршрут к VPN

bind_route_to_vpn
Idempotent

Send traffic of a specified network through a chosen VPN interface or gateway on a Keenetic router using policy-based routing.

Instructions

Направляет трафик указанной сети через уже настроенный на роутере VPN-интерфейс (policy-based routing).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maskYesМаска подсети, например 255.255.255.0
dryRunNoЕсли true — вернуть RCI payload без отправки на роутер (предпросмотр).
metricNoПриоритет маршрута, меньше — приоритетнее (НЕ подтверждено вживую, проверяй на тестовом адресе перед боевым использованием).
targetYesИмя интерфейса или IP шлюза, куда направить маршрут.
confirmNoОбязательно true, чтобы реально применить изменение на роутере.
networkYesАдрес сети, например 10.0.5.0

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • addedInput schema / properties / metric
      Added value: +{
+  "description": "Приоритет маршрута, меньше — приоритетнее (НЕ подтверждено вживую, проверяй на тестовом адресе перед боевым использованием).",
+  "type": "number"
+}
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already indicate this is not read-only and not destructive. The description adds useful context beyond annotations: it clarifies that the VPN interface must already be configured and that the operation is policy-based routing. It does not contradict the 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?

The description is a single, front-loaded sentence with no filler. Every word earns its place, and the parenthetical adds technical precision without bloat.

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?

For a simple routing action, the description plus the fully documented schema and annotations provide enough for an agent to call the tool correctly. The main gap is not mentioning the dryRun/confirm workflow or the need to list available VPN interfaces, but those are partially covered by parameter descriptions and sibling tools.

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 the parameters are already well-documented. The description does not add additional parameter-level meaning beyond saying the traffic of the specified network is routed through a VPN interface, which is already reflected in the 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?

The description clearly states the specific action: directing traffic of a given network through an already-configured VPN interface using policy-based routing. It distinguishes itself from siblings like add_route or unbind_route_from_vpn by specifying the VPN context and policy-based routing nature.

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?

The use case is implied but not explicit: an agent can infer it should be used when routing a network through an existing VPN. However, it does not explicitly say when not to use it, nor does it mention alternatives or prerequisites such as verifying the VPN interface exists.

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