Skip to main content
Glama

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

update_widget_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_widget_hidden_option"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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, so the safety bar is lower, yet the description adds nothing beyond the annotations. It does not say that the existing option value is overwritten, whether the change is reversible, or what permissions are needed, which is significant for a destructive, non-idempotent mutation.

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?

It is a single short sentence with no filler, and the core action is front-loaded. Its brevity is efficient, although it edges toward under-specification rather than true conciseness.

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?

For a destructive, non-idempotent mutation with four required parameters and no output schema, the description omits consequences of the overwrite, prerequisites, and return behavior. An agent could call it but would not understand the impact of doing so.

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% and the schema already explains each field, including how to obtain opt_id from quiz://{id}/widgets_hidden. The description contributes no additional meaning about name/value semantics, so the baseline of 3 applies.

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 states a specific verb and resource: it updates a hidden service option of a quiz widget. That is clearer than a bare restatement of the name, but it never distinguishes this tool from the closely named siblings update_hidden_option or create_widget_hidden_option, so an agent must still infer the boundary between them.

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 when-to-use guidance, no exclusions, and no mention of alternatives such as update_hidden_option. The agent is left to guess whether this applies to widget-scoped options only and when to prefer a sibling.

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