Skip to main content
Glama

Новый опрос

create_quiz

Создает новый опрос в указанной папке.

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": {
      "folder_id": "<folder_id>"
    },
    "name": "create_quiz"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoНазвание опроса (необязательно).
typeNoФормат опроса: regular — своя страница по ссылке (по умолчанию); micro — опрос на сайте, показывается карточкой или модальным окном внутри чужой страницы, подключается к сайту через manage_workspace_sites и manage_quiz_site_placement. Задаётся только при создании, потом не меняется.
ai_typeNoЧто собирать при AI-генерации: quiz — обычный опрос, у вопросов нет правильных ответов; test — тест, где у вариантов проставлены баллы и отмечены правильные ответы, а респондент в конце получает результат. По умолчанию quiz.
projectNoМетка проекта для своего учёта: произвольная строка, которая просто сохраняется у опроса. На поведение опроса не влияет, респондент её не видит. Не просите её у человека сами.
folder_idYesID папки, в которой нужно создать опрос. Взять из folder://list.
with_logicNoПросить ли AI сразу построить логику переходов между вопросами (ветвление по ответам). Без неё вопросы идут подряд. Используется при AI-генерации.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / name / maxLength
      Added value: +80
  2. Changed1 schema field changed
    • addedInput schema / properties / type
      Added value: +{
      +  "description": "Формат опроса: regular — своя страница по ссылке (по умолчанию); micro — опрос на сайте, показывается карточкой или модальным окном внутри чужой страницы, подключается к сайту через manage_workspace_sites и manage_quiz_site_placement. Задаётся только при создании, потом не меняется.",
      +  "enum": [
      +    "regular",
      +    "micro"
      +  ],
      +  "type": "string"
      +}
  3. 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 safety profile is covered structurally. The description adds almost nothing behavioral beyond the annotation layer: it doesn't mention permissions, what happens with an invalid folder_id, the immutability of `type` after creation, or AI-generation side effects flagged in the 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 zero filler, which is efficient. It is arguably too terse for a tool with six parameters and AI-generation options, but nothing is redundant.

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 creation tool with six parameters, two enums and AI-generation flags, the description does not tell the agent which creation path to choose or what the call consequences are. The rich schema compensates for parameter detail, but selection guidance and behavioral context are missing.

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 enum values and defaults fully documented for type, ai_type, project, with_logic and folder_id. The description only echoes the folder requirement, adding no meaning beyond the schema, so the 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?

The description states a specific verb and resource ('Создает новый опрос') plus a scope constraint ('в указанной папке'), so an agent knows exactly what is produced. It does not differentiate itself from siblings such as create_quiz_from_template, which is the closest competing way to create a quiz.

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 or when-not-to-use guidance and no named alternative, even though create_quiz_from_template exists as an obvious sibling choice. Usage is only inferable from the verb 'creates'.

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