Skip to main content
Glama

QR-код опроса

manage_quiz_qr_code
Destructive

QR-код опроса: наклейка на столе, слайд на конференции, листовка у стойки. Показывает текущий код и настройки, собирает новый и убирает логотип из центра. Код ведёт на опубликованный опрос, поэтому неопубликованный опрос получает отказ. Загрузить логотип отсюда нельзя — это делают в кабинете, — но уже загруженный код учитывает. Повторный вызов с теми же настройками отдаёт готовый файл и не пересобирает его: каждая сборка списывает место с тарифа.

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>",
      "action": "<action>"
    },
    "name": "manage_quiz_qr_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNoСторона картинки в точках, 100–1000. По умолчанию — как в прошлый раз, иначе 320.
colorNoЦвет кода, шестизначный HEX вида #000000.
forceNoПересобрать код, даже если настройки не менялись.
actionYesЧто сделать: show — текущий код и настройки, generate — собрать код, delete_logo — убрать логотип из центра.
formatNoФормат файла: png, svg или eps. По умолчанию — как в прошлый раз, иначе png.
marginNoПоля вокруг кода, 0–10. По умолчанию 1.
quiz_idYesID опроса.
backgroundNoЦвет фона, шестизначный HEX вида #ffffff.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations it discloses genuinely useful behavior: unpublished quizzes are rejected, an already-uploaded logo is honored, and each rebuild consumes plan quota, so a repeat call with unchanged settings returns the cached file instead of rebuilding. That quota/caching disclosure is exactly the kind of context annotations cannot carry. The one soft spot is that 'does not rebuild' reads close to idempotency while idempotentHint=false — the force flag reconciles them, but the description never mentions force to explain the difference.

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 sentences, front-loaded with the operations and then layered with constraints; each constraint sentence earns its place. The opening scenario list is the weakest part — decorative rather than directive — but it is short and does set context for what the artifact is.

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?

For an 8-parameter, destructive, no-output-schema tool it covers the essentials an agent needs before calling: what each action does, the publication precondition, the logo limitation, and the quota/caching consequence. It does not describe the shape of what 'show' returns (settings object vs. image) or whether deletion of the logo is reversible, which leaves a small gap on the destructive path.

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 size, color, margin, format, force, quiz_id and the action enum are all documented in the schema itself; the description only refers generically to 'настройки' and never adds format, default, or range meaning. Baseline 3 is appropriate when the schema does all the parameter work.

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 second sentence enumerates the three concrete operations in one-to-one correspondence with the action enum: show the current code and settings, generate a new one, remove the logo from the center. The verb+resource is unambiguous (QR code of a quiz) and no sibling in the catalog handles QR codes, so there is nothing to confuse it with.

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?

The opening sentence gives real-world placement scenarios (sticker, conference slide, counter flyer) and the body states the hard precondition that only a published quiz works, plus an explicit exclusion: logos cannot be uploaded here, that is done in the dashboard. What is missing is any explicit alternative to route to when the quiz is unpublished or when the agent needs to upload a logo — it says 'not here' without naming where.

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