Skip to main content
Glama

Удаление скрытой опции вопроса

delete_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": "delete_widget_hidden_option"
  }
}

Input Schema

NameRequiredDescriptionDefault
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, idempotentHint=false and readOnlyHint=false, so the safety profile is covered structurally. The description adds no behavior beyond that: it does not say whether the deletion is reversible, whether it affects the quiz widget or existing answers, or what happens if the option is referenced elsewhere.

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?

A single, front-loaded sentence with no wasted words. It is efficient, though its brevity reflects under-specification rather than disciplined density.

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 two-parameter destructive delete, the schema is fully documented and annotations carry the safety profile, so the definition is callable as-is. It still omits the effect of deletion on the parent widget and any irreversibility confirmation, which an agent deleting data would benefit from.

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 schema already explains that opt_id comes from quiz://{id}/widgets_hidden. The description adds no parameter meaning beyond the schema, so the baseline 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 names a specific verb ('Удаляет') and a specific resource ('скрытую служебную опцию у виджета опроса'), so an agent knows exactly what object is being removed. It stops short of distinguishing this from the near-identical siblings delete_hidden_option or delete_widget_hidden_option's create/update counterparts, so it does not earn a 5.

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 prerequisite (e.g. the option must exist and how to find it), and no mention of alternatives such as delete_hidden_option. The agent must infer everything from the name alone.

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