Skip to main content
Glama

Удаление переменной опроса

delete_quiz_variable
Destructive

Удаляет скрытую переменную (extra field) из опроса.

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>",
      "field_id": "<field_id>"
    },
    "name": "delete_quiz_variable"
  }
}

Input Schema

NameRequiredDescriptionDefault
quiz_idYesID опроса.
field_idYesUUID скрытой переменной. Взять из quiz://{id}/variables.

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 destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered by structured data. The description adds only a small amount of context by clarifying that the target is a hidden variable / extra field; it says nothing about permanence, whether collected answer data tied to the variable is lost, or whether the quiz itself is affected.

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 short sentence with no wasted words, and the resource being deleted is front-loaded. It is efficient but so terse that it borders on under-specification rather than crispness.

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 tool with full schema coverage and explicit destructive annotations, the description is minimally sufficient to call the tool correctly. It still omits consequences of the deletion and any confirmation or permission expectations, which an agent would want before invoking an irreversible operation.

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 documents both quiz_id and field_id, including the hint to source the UUID from quiz://{id}/variables. The description adds no parameter meaning beyond that, 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: deleting a hidden variable (extra field) from a quiz. This is unambiguous and lets an agent distinguish it from create_quiz_variable and update_quiz_variable by name alone, though it never names those siblings explicitly.

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 or when-not-to-use guidance, no prerequisites, and no mention of alternatives such as update_quiz_variable for renaming instead of removing. The only usage signal is the implicit 'delete means remove', which the name already conveys.

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