Skip to main content
Glama

Загрузка файла в опрос

upload_quiz_media

Загрузка медиа (изображение, видео или аудио) для блока multimedia любого виджета. Передайте type (image|video|audio) и url (ссылка) или file_base64 — файл сохраняется в хранилище, возвращается url. Подставьте url в update_quiz_widgets: multimedia.imgUrl, multimedia.videoUrl или multimedia.audioUrl. Укажите ровно один: 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>",
      "type": "<type>"
    },
    "name": "upload_quiz_media"
  }
}

Input Schema

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

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?

Annotations already declare openWorldHint=true, idempotentHint=false, destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: the file is persisted to storage, a url is returned, the server itself downloads a supplied url, and the warning that url must point at the file rather than a third-party API endpoint.

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-loaded with purpose, then constraint, then downstream usage; four sentences with no filler. Slightly dense but every sentence carries operational information an agent needs before calling.

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

Completeness5/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 supplies the missing return value (the stored url) and the exact place to use it. Combined with the mutual-exclusion rule and url semantics, an agent has everything needed to call this correctly without inspecting siblings.

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 coverage is 100%, so the baseline is 3. The description nonetheless adds meaning the schema only hints at: url and file_base64 are mutually exclusive ('Укажите ровно один'), and url semantics are clarified as a public direct file link that the server will fetch. The filename parameter is not discussed in the description but is fully documented in the schema.

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 names a specific verb and resource ('Загрузка медиа ... для блока multimedia любого виджета') and enumerates the three media types. Scope ('любого виджета') implicitly distinguishes it from the narrower upload_quiz_widget_image sibling, but no sibling is named outright.

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?

It states the post-upload step precisely: take the returned url and place it into update_quiz_widgets at multimedia.imgUrl/videoUrl/audioUrl. It also gives the selection rule between url and file_base64 ('ровно один'). What is missing is any explicit exclusion against sibling uploaders such as upload_quiz_widget_image.

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