Skip to main content
Glama

Применение темы к опросу

apply_quiz_theme
Destructive

Применяет указанную тему оформления к опросу. В ответе возвращает поле quiz с детальной информацией об опросе после применения темы: id, name, url_shared, answer_count, widgets (структура виджетов), hidden_options, folder, created_at, updated_at. Эти данные можно использовать сразу без отдельного чтения quiz://{id}/structure.

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>",
      "theme_id": "<theme_id>"
    },
    "name": "apply_quiz_theme"
  }
}

Input Schema

NameRequiredDescriptionDefault
quiz_idYesID опроса.
theme_idYesID темы.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=true, so the mutation profile is covered structurally. The description adds real value by enumerating the returned quiz fields and telling the agent it can skip a parallel read. What it omits is the destructive dimension: it never says that the existing theme/customizations on the quiz are replaced rather than merged, which is exactly the context an agent needs before calling a destructive tool.

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?

The action statement is front-loaded in the first sentence, and the second sentence earns its length by enumerating the return payload. The field list (id, name, url_shared, answer_count, widgets, hidden_options, folder, created_at, updated_at) is somewhat dense but is the one place where the description delivers non-redundant information.

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

Completeness4/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 carries the return-value burden and does so thoroughly, including a concrete navigation hint (skip quiz://{id}/structure). It is nearly complete for a two-parameter mutation; the remaining gap is that the overwrite/replace semantics flagged by destructiveHint=true are never spelled out.

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% — both quiz_id and theme_id are typed and documented in the schema. The description adds no syntax, format, or constraint information about the parameters beyond restating the intent, so the baseline 3 applies.

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 description names a specific verb and resource — applying a given design theme to a quiz — and additionally specifies what the call returns (the quiz object). This clearly distinguishes it from theme-level siblings such as create_theme, update_theme, or manage_theme, which operate on themes themselves rather than binding one to 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 Guidelines3/5

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

Usage is only implied: the closing sentence hints that the returned payload makes a follow-up call to quiz://{id}/structure unnecessary, which is a useful efficiency cue. However, there is no explicit statement of when to use this versus editing theme definitions, and no prerequisites (ownership/edit rights on the quiz) are mentioned.

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