Skip to main content
Glama
Sign In

АРТпротект

by ru.artprotect
OverviewDiscussionsAdmin

Что делать, если скопировали работу или бренд

infringement_action_plan
Read-onlyIdempotent

Пошаговый план для правообладателя, чью работу (рисунок, принт, фото, дизайн, текст, музыку) или товарный знак используют без разрешения: фиксация доказательств, поиск других копий и продавца, подтверждение прав, жалоба площадке (на Wildberries — «Цифровой арбитраж»), досудебная претензия, иск. Вызывай первым, когда человек пишет, что его работу или бренд скопировали. Возвращает title, steps (номер, название, что сделать, ссылка на статью, какой инструмент вызвать дальше), links и note. Сумму считает estimate_compensation, текст претензии — draft_pretrial_claim.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "infringement_action_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
objectNoЧто скопировали: design — рисунок, принт, дизайн; photo — фото; text — текст; trademark — товарный знак или бренд; music — музыка; other — другоеdesign
marketplaceNoГде нарушение: wildberries, ozon, yandex_market — маркетплейсы; site — сайт или соцсеть; other — другоеwildberries

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / marketplace / description
      Added value: +"Где нарушение: wildberries, ozon, yandex_market — маркетплейсы; site — сайт или соцсеть; other — другое"
    • addedInput schema / properties / object / description
      Added value: +"Что скопировали: design — рисунок, принт, дизайн; photo — фото; text — текст; trademark — товарный знак или бренд; music — музыка; other — другое"
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already establish that this is a safe read-only, idempotent, non-open-world operation. The description adds useful behavioral context by specifying the returned fields and by naming which tools handle follow-up actions, though it does not discuss deeper operational caveats.

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?

The description is front-loaded with the purpose and then efficiently covers the step preview, invocation timing, return shape, and related tools. Every sentence contributes actionable information.

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?

There is no output schema, so the description appropriately explains the return structure: title, steps, links, and note. With fully described parameters and annotations covering the safety profile, an agent has enough context to invoke it correctly.

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 both parameters are fully enumerated with descriptions. The tool description mentions example work types and Wildberries specifically, but does not add meaning beyond the schema for the full parameter set.

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 resource and action: a step-by-step action plan for a rights holder whose work or trademark was copied. It also distinguishes this tool from siblings by naming estimate_compensation and draft_pretrial_claim for adjacent tasks.

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 explicitly says to call this tool first when someone reports that their work or brand was copied. It also routes related needs to the correct alternatives, naming estimate_compensation for damages and draft_pretrial_claim for the demand letter.

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

All АРТпротект 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