Skip to main content
Glama
Sign In

24Repost

by io.github.24repost-ru
OverviewDiscussionsAdmin

route_set_replacements

Задаёт замены маршрута: замены текста (найти и заменить; пустая замена удаляет найденное — так убирают «подвал» чужого поста) и подмену ссылок. Замены применяются по порядку списка: одна может подготовить текст для следующей. Прежние замены заменяются переданными; стоп-слова, старт-слова, фильтры вложений и остальные правила остаются как есть, поэтому сначала прочитайте нынешние замены (route.show) и передайте их вместе с изменениями. Пустой список снимает все замены.

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

Input Schema

NameRequiredDescriptionDefault
routeIdYesНомер маршрута — из списка маршрутов человека (действие routes.list).
replacementsYesВсе замены маршрута в порядке применения: замена текста (replace_text — найти и заменить; пустая замена удаляет найденное, так убирают «подвал» чужого поста) и подмена ссылки (replace_link). Прежние замены заменяются этим списком; пустой список снимает все замены.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and openWorldHint=false, so the description carries the real burden and does well: it discloses the destructive replace-all semantics, the preserved-settings side effect, and the order-dependent application of rules. It stops short of stating the response shape or whether changes are reversible, so it is not a full 5.

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?

It is front-loaded with the destructive replace-all warning and the prerequisite read, which is the right ordering. Some content is duplicated between the prose and the nested schema description (notably the "подвал чужого поста" deletion example), costing a little tightness.

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 definition covers everything an agent needs: what the lists mean, application order, preservation of other rules, the read-before-write workflow, and the clearing behavior. No material gap remains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so a baseline of 3 is warranted; the description raises this by adding semantics not present in the schema — that replacements apply sequentially in list order and that one rule can prepare text for the next, plus the empty-list-clears-all contract at the top level.

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 opens with a specific verb and resource ("Задаёт замены маршрута") and immediately enumerates the two rule kinds it accepts — text find/replace and link substitution — so an agent can distinguish it from sibling setters like route_set_words or route_set_utm 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 Guidelines5/5

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

It gives explicit operational guidance: read current replacements via route.show first and re-send them together with your changes, because this tool replaces the whole list; an empty list removes all replacements. It also states what is NOT affected (stop words, start words, attachment filters), which is exactly the boundary information an agent needs to avoid clobbering unrelated config.

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