Skip to main content
Glama

Опрос из шаблона

create_quiz_from_template

Создаёт свой опрос из шаблона каталога — со всеми вопросами, логикой и оформлением. Дальше его правят обычными инструментами. Опрос создаётся черновиком: респонденты увидят его после publish_quiz. template_id берётся из search_quiz_templates.

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

Input Schema

NameRequiredDescriptionDefault
nameNoСвоё название опроса. По умолчанию берётся название шаблона.
folder_idYesID папки, в которой создать опрос (folder://list).
template_idYesID шаблона из search_quiz_templates.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / name / maxLength
      Added value: +80
  2. First observed

TDQS

A3.8/5.0
Behavior3/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 mutation semantics are covered structurally. The description adds genuinely useful behavior the annotations cannot convey: the new quiz is created as a draft and is invisible to respondents until publish_quiz is called. It does not mention that repeated calls produce duplicate quizzes despite idempotentHint=false, nor what the response contains.

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?

Four short sentences, each earning its place: what is created, how it is edited afterwards, the draft/publish gate, and where the ID comes from. The draft warning is front-loaded near the end with no filler.

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?

With no output schema, the description never states what is returned — critically, whether the new quiz's ID comes back so the agent can chain into publish_quiz or editing tools. Draft state and next-steps are well covered, but this return-value gap matters for a creation tool meant to be chained.

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 coverage is 100% and the schema already explains name defaulting, folder_id origin (folder://list) and template_id origin, so the description adds little beyond restating where template_id comes from. Baseline 3 is appropriate when the schema carries the parameter semantics.

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 verb 'Создаёт' plus the resource 'свой опрос из шаблона каталога' is specific, and it clarifies the scope ('со всеми вопросами, логикой и оформлением') that distinguishes it from create_quiz (empty quiz) and make_quiz_template (the inverse direction). An agent can identify the operation without opening the schema.

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

Usage Guidelines4/5

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

It explicitly names the prerequisite source (template_id из search_quiz_templates) and the follow-up gate (publish_quiz) for visibility, plus that further changes go through regular tools. It stops short of an explicit 'use create_quiz instead when starting from scratch' exclusion, but the context is clear.

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