Skip to main content
Glama

Копия опроса

duplicate_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": {
      "quiz_id": "<quiz_id>"
    },
    "name": "duplicate_quiz"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoОпциональное название нового опроса (максимум 80 символов).
quiz_idYesID опроса, который нужно дублировать.
folder_idNoID папки, в которую положить копию. По умолчанию копия ложится рядом с оригиналом. Копирование в другую папку требует отдельного права.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive, closed-world mutation. The description adds real value by stating the copy carries all data and versions, but it does not clarify what is excluded (statistics, webhooks, integrations, sharing settings), whether the copy is independent of the original, or what identifier is returned.

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, stating the action and the copy scope immediately. It is efficient, though the extreme brevity leaves behavioral questions unanswered rather than being wasteful.

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 three-parameter mutation tool with full schema coverage and no output schema, the description covers the core action but omits what the returned copy looks like and what exactly is or is not duplicated, which matters for a duplication tool. Adequate but with clear gaps.

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%, so the schema already explains quiz_id, the optional name with its 80-character cap, and the folder_id default and permission requirement. The description adds no parameter-level meaning beyond that, 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 gives a specific verb and resource ('Создает копию существующего опроса') plus the scope of the copy ('со всеми данными и версиями'), which distinguishes it from create_quiz or create_quiz_from_template. It does not name any sibling explicitly, so it stops short of a 5.

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?

The phrase 'существующего опроса' implies you need an existing quiz, but there is no explicit when-to-use guidance, no mention of when to prefer create_quiz or create_quiz_from_template instead, and no note about prerequisites such as the extra permission for folder_id mentioned only in the schema.

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