Skip to main content
Glama

Новая скрытая опция вопроса

create_widget_hidden_option

Создает скрытую служебную опцию для виджета опроса. widget_uuid — один из UUID из quiz://{id}/structure (поле ids); не придумывайте id, берите из структуры.

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>",
      "widget_uuid": "<widget_uuid>",
      "name": "<name>",
      "value": "<value>"
    },
    "name": "create_widget_hidden_option"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesКлюч скрытой опции виджета.
valueYesЗначение опции.
quiz_idYesID опроса.
widget_uuidYesUUID виджета (формат xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). Обязательно взять из quiz://{id}/structure, поле ids; не генерировать свой.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the agent knows this is a non-destructive, non-idempotent write. The description adds the 'служебная' (internal/service) nature of the option and the prerequisite that the widget must already exist in the structure. It does not say what happens on duplicate name, whether existing values are overwritten, or what is returned.

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?

Two short sentences with the purpose front-loaded and the critical uuid constraint immediately after; no filler. Slightly redundant with the schema's widget_uuid description, which repeats the same rule verbatim.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-required-param write tool with no output schema, the definition covers the action and the riskiest parameter correctly, and annotations carry the safety profile. It remains thin on what a hidden option is used for, how it differs from quiz-level hidden options, and duplicate-handling behavior.

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%, including the same instruction that widget_uuid must come from quiz://{id}/structure and not be generated — the description largely restates that schema text rather than adding meaning. No additional semantics are given for name, value, or quiz_id beyond what the schema documents.

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: creates a hidden service option for a quiz widget, which is more precise than the bare tool name. It does not, however, distinguish this from the sibling create_hidden_option (quiz-level) — the widget-vs-quiz scope difference is only implied by the phrase 'для виджета опроса'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no mention of alternatives such as create_hidden_option, update_widget_hidden_option, or get_quiz_hidden_options. The only guidance given ('take the uuid from quiz://{id}/structure') is a parameter precondition, not a routing rule.

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