АРТпротект

Черновик досудебной претензии нарушителю

draft_pretrial_claim

Read-onlyIdempotent

Собирает текст досудебной претензии продавцу, который использует работу или товарный знак без разрешения: стороны, факты, нормы ГК РФ (в ред. 214-ФЗ), требования (прекратить использование и выплатить компенсацию в срок), приложения. Ничего не отправляет и не сохраняет. Вызывай, когда человек хочет написать продавцу претензию; сумму требования сначала оцени через estimate_compensation. Возвращает markdown (текст претензии с пометками [в скобках] на месте недостающего), missing (чего не хватает), checklist (что подготовить) и how_to_send (как отправить). Данные спрашивай у самого правообладателя; продавца — из карточки «О продавце» на маркетплейсе.

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": {
      "claimant": "<claimant>",
      "infringer": "<infringer>",
      "work": "<work>",
      "listing": "<listing>"
    },
    "name": "draft_pretrial_claim"
  }
}

Input Schema

Name	Required	Description
`work`	Yes	Работа или знак, права на который нарушены
`demand`	No	Требования: сумма, срок, реквизиты
`listing`	Yes	Карточка товара с нарушением
`claimant`	Yes	Правообладатель — от чьего имени претензия
`infringer`	Yes	Нарушитель — продавец с маркетплейса

Schema Changelog

Changes observed during successful MCP inspections.

Changed23 schema fields changedOct 23, 2026

addedInput schema / properties / claimant / properties / address / description
```
Added value: +"Почтовый адрес для ответа"
```
addedInput schema / properties / claimant / properties / email / description
```
Added value: +"Почта для ответа"
```
addedInput schema / properties / claimant / properties / inn / description
```
Added value: +"ИНН, если ИП или компания"
```

addedInput schema / properties / claimant / properties / ogrn / description

Added value: +"ОГРН или ОГРНИП, если ИП или компания"

addedInput schema / properties / claimant / properties / phone / description
```
Added value: +"Телефон для ответа"
```

addedInput schema / properties / demand / description

Added value: +"Требования: сумма, срок, реквизиты"

addedInput schema / properties / demand / properties / amount_rub / description

Added value: +"Сумма компенсации, ₽; пусто — без суммы"

addedInput schema / properties / demand / properties / bank_details / description

Added value: +"Реквизиты для оплаты; пусто — «сообщим по запросу»"

addedInput schema / properties / demand / properties / deadline_days / description

Added value: +"Срок исполнения, дней: 7–90, по умолчанию 30"

addedInput schema / properties / infringer / description

Added value: +"Нарушитель — продавец с маркетплейса"

addedInput schema / properties / infringer / properties / inn / description

Added value: +"ИНН продавца из карточки «О продавце»"

addedInput schema / properties / infringer / properties / kind / description

Added value: +"person — физлицо, ip — ИП, org — компания"

addedInput schema / properties / infringer / properties / ogrn / description
```
Added value: +"ОГРН или ОГРНИП продавца"
```

addedInput schema / properties / listing / description

Added value: +"Карточка товара с нарушением"

addedInput schema / properties / listing / properties / marketplace / description
```
Added value: +"Маркетплейс карточки"
```
addedInput schema / properties / listing / properties / product_title / description
```
Added value: +"Название товара в карточке"
```

addedInput schema / properties / work / description

Added value: +"Работа или знак, права на который нарушены"

addedInput schema / properties / work / properties / created_at / description
```
Added value: +"Когда работа создана"
```
addedInput schema / properties / work / properties / deposit_date / description
```
Added value: +"Дата депонирования"
```

addedInput schema / properties / work / properties / kind / description

Added value: +"drawing — рисунок, photo — фото, design — дизайн или принт, text — текст, video — видео, trademark — товарный знак"

addedInput schema / properties / work / properties / published_url / description

Added value: +"Где работа опубликована раньше копии"

addedInput schema / properties / work / properties / rights_basis / description

Added value: +"author — сам автор, contract — права по договору, employer — служебное произведение"

addedInput schema / properties / work / properties / trademark_number / description

Added value: +"Номер свидетельства на товарный знак"

First observedOct 23, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Adds behavior beyond the annotations: 'Ничего не отправляет и не сохраняет' confirms and sharpens the readOnly/non-destructive profile, and the description discloses the four return elements (markdown with [bracketed] placeholders, missing, checklist, how_to_send) that no output schema exists to convey.

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?

Five sentences, front-loaded with the resource and scope, then the non-side-effect guarantee, the routing rule, the return shape, and the data-sourcing hint. Each sentence carries information the schema and annotations do not.

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 4-required-param nested-object tool with no output schema, it covers what is produced, what is not done (no sending/saving), how placeholders handle missing data, and where inputs come from. An agent has everything needed to call it correctly.

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 baseline is 3; the description earns extra by telling the agent where to source values — claim data from the rights holder itself, seller data from the marketplace's «О продавце» card — which maps directly onto claimant/infringer fields. It does not add format or validation detail beyond 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?

States a specific verb and resource — 'Собирает текст досудебной претензии продавцу' — and enumerates the sections it produces (стороны, факты, нормы, требования, приложения). An agent can distinguish it from estimate_compensation or infringement_action_plan without opening either 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?

Explicit trigger: 'Вызывай, когда человек хочет написать продавцу претензию', plus an ordered alternative — 'сумму требования сначала оцени через estimate_compensation' — naming the sibling and the sequencing condition. Nothing is left to inference.

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

All АРТпротект tools Inspect

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

Need Help?