Skip to main content
Glama
Sign In

24Repost

by io.github.24repost-ru
OverviewDiscussionsAdmin

route_set_two_way

Включает или выключает пересылку в обе стороны для маршрута. Включение заводит встречный маршрут (из приёмника в источник) с теми же настройками и в том же состоянии; выключение снимает встречный, если у него нет своих правил. Встречный маршрут занимает место в пределе тарифа, как обычный; стена сообщества ВКонтакте встречным приёмником — только если публикация на стену открыта.

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": {
      "routeId": "<routeId>",
      "twoWay": "<twoWay>"
    },
    "name": "route_set_two_way"
  }
}

Input Schema

NameRequiredDescriptionDefault
twoWayYestrue — включить пересылку в обе стороны (завести встречный маршрут); false — оставить пересылку в одну сторону (снять встречный маршрут).
routeIdYesНомер маршрута — из списка маршрутов человека (действие routes.list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false and openWorldHint=false; the description goes well beyond that with the side effect of creating a mirrored route, its removal semantics, quota consumption ('занимает место в пределе тарифа'), and a platform-specific constraint for the VKontakte community wall. This is the kind of hidden consequence an agent cannot infer from structured fields.

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?

Three sentences, front-loaded with the action and then the consequences of each branch. Every clause carries information — side effect, removal condition, quota, platform caveat — with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter mutation with no output schema, the description covers the side effects, the conditional removal behavior, quota impact, and a platform edge case. Nothing an agent needs in order to call this correctly appears to be missing.

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 spells out true→create counter-route, false→remove counter-route, so the description mostly restates it. The added value is contextual (the counter-route consumes a tariff slot, VK wall caveat) rather than new meaning for the parameters themselves, so the baseline of 3 applies.

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 names a specific verb and resource: 'Включает или выключает пересылку в обе стороны для маршрута'. The 'two-way forwarding' concept is distinct enough from siblings like route_set_rules or route_configure that an agent can select it without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains the consequences of both parameter values and the conditional case where disabling does not remove the counter-route ('если у него нет своих правил'), which is real guidance on when the effect will or won't occur. It doesn't compare against an alternative way to achieve the same result (e.g. route_create), so it stops short of explicit alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All 24Repost toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources