Skip to main content
Glama

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

delete_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_hidden_option"
  }
}

Input Schema

NameRequiredDescriptionDefault
opt_idYesID скрытой опции. Взять из quiz://{id}/hidden_options.
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 nothing beyond that — it does not warn that the deletion is permanent, whether it cascades to collected data, or whether confirmation/permissions are required. For an irreversible mutation with no output schema, that is a meaningful gap.

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 wasted words, but its brevity is under-specification rather than efficiency. There is no front-loaded warning or scoping detail that would help an agent act correctly.

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?

The tool is simple (2 required integers, full schema coverage, no output schema) and annotations carry the destructive flag, so the minimal description is close to sufficient. It still omits the reversibility/permission context an agent would want before invoking a destructive delete.

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%: both quiz_id and opt_id are documented, and the schema even tells the agent to source opt_id from quiz://{id}/hidden_options. The description adds no additional meaning, 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 sentence names a specific verb and resource: deleting a hidden service option of a quiz ('Удаляет скрытую служебную опцию опроса'). An agent can tell it targets hidden options rather than quiz answers or variables. It does not, however, distinguish itself from the closely named sibling delete_widget_hidden_option, leaving ambiguity between quiz-level and widget-level hidden options.

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 precondition (e.g. the option must already exist), and no mention of the sibling tools that create/update hidden options or of the widget-level variant. The agent must infer everything about selection 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