Skip to main content
Glama

Новый список промокодов

create_promocode_group

Создает новый список промокодов для workspace опроса.

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>",
      "name": "<name>",
      "codes": "<codes>"
    },
    "name": "create_promocode_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesНазвание списка промокодов (max 255 символов).
codesYesМассив строковых кодов для добавления в список (до 1000, каждый max 250 символов).
quiz_idYesID опроса.

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, idempotentHint=false and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that — it does not say what happens if a list with the same name exists, whether codes are validated/deduplicated, or what the call returns given there is no output schema.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though its brevity is part of why coverage elsewhere is thin.

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

Completeness3/5

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

For a mutation tool with three fully documented required parameters and clear annotations, the definition is minimally adequate to invoke correctly. It stops short of explaining behavior on duplicates, name conflicts, or the relationship to the promo-code management siblings an agent will likely need next.

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 name, codes and quiz_id each documented including the 255/250/1000 character limits. The description mentions only that the list belongs to a survey workspace, which the schema's quiz_id already conveys, so baseline 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?

States a specific verb and resource: 'Создает новый список промокодов' (creates a new promo code list), scoped to a survey's workspace. The action is unambiguous, but it offers no differentiation from close siblings such as add_promocodes or manage_promocode_group, which also operate on promo code lists.

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 when-to-use guidance at all. The description does not explain when to create a new list versus adding codes to an existing one via add_promocodes, nor does it state prerequisites such as needing an existing quiz_id or whether name collisions are rejected.

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