Skip to main content
Glama

Собрать шаг правила продаж выключенным

create_sales_rule

Шаг правила продаж, ВСЕГДА выключенный: включает его владелец в кабинете, до этого он ничего не делает. Повод: event tag (tag_id, метка поставлена на сделку) или stage (stage_id, сделка перешла на этап). delay_minutes: через сколько. action: bot (funnel_id, запустить воронку бота), tag_add или tag_remove (target_tag_id), stage (target_stage_id, «Оплачено» нельзя), task (task_text, task_days), goal (цель Метрики). skip_if_replied: не делать, если человек ответил.

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": "create_sales_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalNo
eventNo
actionNo
tag_idNo
stage_idNo
funnel_idNo
task_daysNo
task_textNo
lost_reasonNo
delay_minutesNo
target_tag_idNo
Idempotency-KeyNoКлюч повтора, до 120 знаков. Новый на каждое новое создание; тот же, если повторяете этот вызов после ошибки или обрыва: второй раз ничего не создастся, вернётся первый ответ. Ключ помнится сутки.
skip_if_repliedNo
target_stage_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / Idempotency-Key
      Added value: +{
      +  "description": "Ключ повтора, до 120 знаков. Новый на каждое новое создание; тот же, если повторяете этот вызов после ошибки или обрыва: второй раз ничего не создастся, вернётся первый ответ. Ключ помнится сутки.",
      +  "maxLength": 120,
      +  "type": "string"
      +}
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

The key non-obvious behavior is disclosed: the rule is inserted disabled and is inert until a human enables it, which annotations (readOnlyHint=false, destructiveHint=false) do not convey. It also adds a real business constraint ('«Оплачено» нельзя' for stage targets). However, it says nothing about what is returned, what happens with partial/conflicting triggers, or how retries interact with the Idempotency-Key parameter that the schema documents.

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?

Front-loaded with the single most important fact (always disabled), then a compact trigger/action/delay breakdown in one paragraph. Dense but efficient for 14 parameters; some shorthand ('Повод', 'цель Метрики') trades clarity for brevity.

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 mutation tool with 14 optional parameters, no output schema, and near-zero schema descriptions, the description supplies the domain model needed to fill the arguments correctly, including a hard constraint on stage targets. It stops short of stating which parameters pair with which trigger/action explicitly or describing the response.

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?

With schema description coverage at 7%, the description must carry the parameter burden and largely does: it maps event→tag_id/stage_id, delay_minutes, action→funnel_id/target_tag_id/target_stage_id/task_text/task_days/goal, and explains skip_if_replied. Gaps remain: the literal allowed values of event and action are only implied by prose, and lost_reason and Idempotency-Key are not mentioned at all.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (a sales-rule step) and states its defining property unambiguously: it is created ALWAYS disabled and does nothing until the owner enables it in the cabinet. That distinguishes it from update_sales_rule, though the creation verb itself is only implied by the title ('Собрать') rather than stated in the body.

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

Usage Guidelines3/5

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

Usage is conveyed indirectly through the trigger ('Повод: event … или stage …') and action catalog, which tells the agent what shapes a valid rule. There is no explicit when-to-use vs. update_sales_rule guidance, no statement of prerequisites, and no note on when not to call it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources