Skip to main content
Glama

Правка скрытой опции опроса

update_hidden_option
Destructive

Обновляет скрытую служебную опцию опроса.

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>",
      "opt_id": "<opt_id>",
      "name": "<name>",
      "value": "<value>"
    },
    "name": "update_hidden_option"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesНовый ключ опции.
valueYesНовое значение опции.
opt_idYesID скрытой опции. Взять из quiz://{id}/hidden_options.
quiz_idYesID опроса.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, which is the key safety signal; the description adds nothing beyond that. It does not say what 'обновление' overwrites, whether existing keys can be renamed destructively, or what permissions are needed for this mutation. Nothing contradicts the annotations, but the description carries no weight of its own.

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

Conciseness3/5

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

A single short sentence with no padding, but it is not front-loaded with anything actionable — it is minimal to the point of being uninformative rather than efficiently concise.

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

Completeness2/5

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

This is a destructive four-parameter mutation with no output schema and no annotations narrative; the description should explain what happens on update (overwrite semantics, renaming of keys, idempotency caveats) but instead offers one generic clause. Relative to the tool's complexity, it is substantially under-described.

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 coverage is 100% and the parameter descriptions (including the pointer to quiz://{id}/hidden_options for opt_id) are already informative. The description adds no parameter meaning, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description restates the name and title almost verbatim: 'Обновляет скрытую служебную опцию опроса' adds only the qualifiers 'скрытую' and 'опроса' beyond what the title already says. It gives no indication of how this differs from the very similar siblings update_widget_hidden_option or create_hidden_option, so an agent cannot discriminate on purpose alone.

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?

No when-to-use guidance, no prerequisites, and no mention of when to prefer update_widget_hidden_option instead. The agent must infer the quiz-vs-widget distinction entirely from the tool names.

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