Skip to main content
Glama

Добавление промокодов

add_promocodes

Добавляет новые промокоды в существующий список.

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": {
      "quiz_id": "<quiz_id>",
      "list_id": "<list_id>",
      "codes": "<codes>"
    },
    "name": "add_promocodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
codesYesМассив строковых кодов для добавления (до 1000, каждый max 250 символов).
list_idYesID списка промокодов. Взять из promocode://list.
quiz_idYesID опроса в нужном workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the description needs to add context beyond that. Yet it says nothing about the important consequence of non-idempotency: whether duplicate codes are rejected, silently skipped, or duplicated. It also omits any error or partial-failure behavior, even though up to 1000 codes are submitted in one call.

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?

The description is a single front-loaded sentence with zero waste. It is efficient, though the terseness borders on under-specification for a batch mutation tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a non-idempotent batch mutation that accepts up to 1000 codes and has no output schema, the description should explain what happens on success or partial failure and how duplicates are handled. As written, an agent cannot predict the result of a call beyond 'codes get added'.

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%, with each of the three required parameters documented, including the 1000-item and 250-character limits and the promocode://list reference. The description adds no meaning beyond the schema, so the baseline of 3 applies.

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 states a specific verb and resource: it adds new promo codes to an existing list. This makes the operation distinguishable from creation-type siblings such as create_promocode_group. It does not, however, explicitly name or contrast itself with any sibling tool.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives (e.g. create_promocode_group), no stated prerequisites, and no exclusions. The phrase 'into an existing list' only weakly implies that the list must already exist.

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