Skip to main content
Glama

Вопрос в избранное

save_favorite_question
Destructive

Сохраняет вопрос в библиотеку аккаунта, а с указанным favorite_question_id — перезаписывает уже сохранённый. В библиотеке лежит снимок: правка исходного опроса библиотеку не меняет, и наоборот. До 100 вопросов на воркспейс.

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": {
      "workspace_id": "<workspace_id>",
      "name": "<name>",
      "widget_type": "<widget_type>",
      "data": "<data>"
    },
    "name": "save_favorite_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesСнимок вопроса — объект виджета из quiz://{id}/structure. До 64 КБ.
nameYesНазвание в библиотеке, до 255 символов.
choice_typeNoДля вопросов выбора: text или image.
widget_typeYesТип вопроса, как в структуре опроса (choice, input, matrix и т.д.).
workspace_idYesID воркспейса (из workspace://list).
source_quiz_idNoОпрос, из которого взят вопрос. Необязательно, только для справки.
choice_multipleNoДля вопросов выбора: разрешено несколько ответов.
source_widget_idNoUUID вопроса в этом опросе. Необязательно, только для справки.
favorite_question_idNoID сохранённого вопроса для перезаписи. Не передавайте, чтобы добавить новый.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, and the description earns extra credit by explaining the snapshot model — editing the source quiz does not mutate the library and vice versa — plus the 100-questions-per-workspace quota. It never explicitly states that overwriting discards the previously saved entry or what happens when the limit is reached, which is the remaining gap for a destructive write.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the primary save action and no filler. Each sentence contributes a distinct fact: create/overwrite branching, snapshot semantics, quota.

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 9-parameter destructive write with nested data and no output schema, the description covers the semantics an agent most needs — the create/overwrite switch, snapshot independence, and the workspace quota. It omits the return value (e.g. the new favorite_question_id) and the failure mode at the quota limit, which would round it 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%, so the schema already carries parameter meaning, and much of the description's favorite_question_id explanation restates what the property description says. It does add conceptual value by framing 'data' as a snapshot decoupled from the source quiz, which the schema does not convey.

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 ('Сохраняет вопрос в библиотеку аккаунта') and immediately splits the behaviour into create-versus-overwrite keyed on favorite_question_id, so an agent can tell exactly what the call does without opening the schema. This also distinguishes it from the delete/get siblings in the library family.

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 clearly conditions overwrite behaviour on supplying favorite_question_id and implies the plain-save path otherwise, giving a usable when-to-use rule. It stops short of explicit exclusions (e.g. when to prefer editing the source quiz instead, or what to do at the 100-question ceiling), so it is strong but not a full when/when-not statement.

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