Skip to main content
Glama
Sign In

24Repost

by io.github.24repost-ru
OverviewDiscussionsAdmin

route_configure

Меняет основные настройки маршрута: своё название, подпись автора, заголовок-ссылку на канал, пересылку собственных сообщений бота. Меняются только переданные поля, остальные остаются как были. Текст до и после копии, правила, приёмник и группа настраиваются другими действиями.

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>"
    },
    "name": "route_configure"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoНазвание маршрута до 64 знаков. Пустая строка или null — убрать своё название: маршрут будет назван по чатам.
routeIdYesНомер маршрута — из списка маршрутов человека (действие routes.list).
showAuthorNoСтавить перед текстом копии имя автора сообщения («Иван: …»). Включают для групп; у постов канала автора нет.
ownMessagesNoПересылать и сообщения самого бота (например, посты по расписанию). Обычно выключено.
showChannelTitleNoНад текстом копии ставить название канала-источника со ссылкой на него. Только для маршрутов из канала.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and openWorldHint=false, and the description adds a genuinely important behavioral fact beyond them: partial-update semantics ("Меняются только переданные поля, остальные остаются как были"), which is not derivable from the schema. It does not cover permissions, reversibility, or whether an empty update is a no-op, so it is not exhaustive.

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 short sentences, scope first, partial-update rule second, boundary/exclusion last. No filler, and each sentence carries distinct information.

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 small mutation tool with full schema documentation and no output schema, the description covers purpose, field scope, update semantics, and boundaries. Missing only peripheral detail such as what an all-null payload does or whether changes are immediately visible.

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 schema already explains all five parameters in detail, including null/empty-string behavior for name and the channel-only constraint on showChannelTitle. The description only hints at the field set and adds no format or edge-case meaning beyond it; baseline 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?

States a specific verb and resource ("Меняет основные настройки маршрута") and enumerates exactly which settings are in scope: name, author signature, channel-title link, own-message forwarding. It explicitly disclaims the fields owned by siblings (frame text, rules, target, group), so an agent can distinguish it from route_set_frame_text, route_set_rules, route_change_target without opening schemas.

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?

Gives clear context for use (editing the four 'main' settings) and explicit exclusions pointing to "другими действиями" for everything else. It stops short of naming the specific sibling tools an agent should call instead, so routing still requires a small inference step.

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