Skip to main content
Glama

Картинка к варианту ответа

upload_quiz_widget_image

Загрузка изображения для виджета «выбор с медиа» (варианты ответа с картинкой). Передайте url (ссылка на картинку) или file_base64 (содержимое в base64) — файл сохраняется в хранилище, возвращается url. Подставьте полученный url в choiceImageEntities[].link в update_quiz_widgets. Укажите ровно один: url или file_base64. url — публичная ссылка на саму картинку: сервер скачает её к себе; это не адрес чужого API.

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

Input Schema

NameRequiredDescriptionDefault
urlNoСсылка на изображение. Скачаем и сохраним в хранилище. Укажите url или file_base64.
quiz_idYesID опроса.
filenameNoИмя файла с расширением (для file_base64). Опционально, по умолчанию image.jpg.
file_base64NoИзображение в base64 (можно с префиксом data:image/...;base64,...). Укажите url или file_base64.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Adds useful operational detail beyond the annotations: the file is saved to storage, a URL is returned, exactly one of url or file_base64 must be supplied, and url is a public image link that the server downloads rather than an API endpoint. The annotations already declare non-readonly, open-world, non-idempotent, and non-destructive behavior, so this additional context earns a 4 even though duplicate-upload effects and permission requirements are not discussed.

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?

Front-loads the purpose and then gives compact operational instructions, including the downstream field where the returned URL belongs. The repeated mention of url/file_base64 is justified by the exactly-one rule, so the description is efficient overall with only minor redundancy.

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 a four-parameter upload tool with no output schema, the description covers what is saved, what is returned, mutual exclusivity of inputs, and how the returned URL is consumed downstream. The required quiz_id is left to the schema, but schema coverage is complete; overall the definition is complete enough for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3; the description still adds the exactly-one constraint between url and file_base64 and clarifies that url must be a public image link the server downloads, not an API address. It adds little about quiz_id or filename beyond what the schema already says, so 4 is appropriate.

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?

States a specific verb (Загрузка) and resource (изображения) and narrows the scope to the «выбор с медиа» widget and answer options with images. This makes the purpose clear enough to distinguish from generic quiz uploads by context, but it does not name or explicitly contrast with an alternative upload tool.

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?

Provides clear usage context: use it for media-choice widget answer images and place the returned URL into choiceImageEntities[].link in update_quiz_widgets. It does not state when not to use it or name an alternative upload tool, so it falls short of the explicit when/when-not/alternatives bar for a 5.

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