Skip to main content
Glama

Опрос как шаблон

make_quiz_template

Создает шаблон на основе текущего опроса.

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": "make_quiz_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
quiz_idYesID опроса для сохранения в шаблоны.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/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 safety is partly covered. The description adds nothing beyond that: it does not say that each call creates a separate new template (the non-idempotent consequence), whether it overwrites an existing template, what permissions are needed, or what the caller receives.

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?

One short, front-loaded sentence with no filler. It is efficient, though its brevity borders on under-specification rather than true conciseness.

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 one-parameter, non-destructive creation tool with full schema coverage and annotations, the description is minimally adequate. It leaves a meaningful gap, however, by not explaining how the created template relates to the source quiz or how it differs from the create_quiz_from_template sibling.

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 single quiz_id parameter is fully documented in the schema, so baseline 3 applies. The description adds no extra meaning about the parameter and even introduces mild confusion with the phrase "текущего опроса".

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/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 ("Создает шаблон" — creates a template), but the framing "на основе текущего опроса" (based on the current quiz) is ambiguous: the tool actually takes a quiz_id, so "current" doesn't match the schema. It also never distinguishes itself from the closely related sibling create_quiz_from_template, which performs the inverse operation.

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 create_quiz_from_template or the other template-related siblings, and no mention of prerequisites or side effects. The agent must infer from the name alone that this is the direction 'quiz → template' rather than 'template → quiz'.

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