Skip to main content
Glama
Kykyryky23

keenetic

by Kykyryky23
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Добавить маршрут

add_route
Idempotent

Adds a static route to a Keenetic router, specifying network, subnet mask, and target gateway or interface, with optional metric and dry-run preview before applying.

Instructions

Добавляет статический маршрут.

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

C2.9/5.0
Behavior2/5

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the mutation profile is known. However, the description adds no behavioral context beyond the core action, such as the need to set confirm=true for real changes or that dryRun provides a preview; these details live only in the schema.

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 a single, efficient sentence with no filler. It is front-loaded and immediately communicates the tool's purpose, though it is quite terse given the tool's six parameters.

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?

The schema is rich enough to support invocation, and annotations cover the safety profile. However, the description does not help an agent choose this tool over closely related route-management siblings, and there is no output schema or return-format guidance, leaving some selection and post-invocation ambiguity.

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%, and the schema already documents each parameter, including the caveat about metric and the confirm/dryRun behavior. The description itself adds no parameter-level meaning, so the baseline of 3 is appropriate.

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?

The description states a clear verb and resource: 'Добавляет статический маршрут' ('Adds a static route'). The word 'static' helps distinguish it from route-related siblings such as add_domain_route, though it does not explicitly name them.

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?

The description gives no guidance on when to use this tool versus alternatives like add_domain_route, run_route_batch, or bind_route_to_vpn. There is no mention of prerequisites, confirmation requirements, or dry-run usage, so an agent must infer context entirely from the schema and annotations.

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