Skip to main content
Glama

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

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

Input Schema

NameRequiredDescriptionDefault
quiz_idYesID опроса для удаления.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, so the key added value is that this is a soft delete with a restoration path, which materially softens the destructive profile and tells the agent the action is recoverable. It stops short of saying how or where to restore, or what permissions are required, which keeps it below a 5.

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

Conciseness5/5

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

A single short sentence that front-loads the action and immediately qualifies it with the deletion semantics. No filler, nothing repeated from the title alone.

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 one-parameter tool with full schema coverage, annotations, and no output schema, the description covers the essential outcome (soft delete, recoverable). It omits the restore route and any permission or cascade notes, leaving a modest gap.

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?

Only one parameter (quiz_id) exists and schema description coverage is 100%, so the schema fully documents it. The description adds no format, range, or validity detail beyond the schema, which is the baseline-3 case.

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 ('Удаляет опрос') plus the deletion mode (soft delete, restorable), so the agent knows exactly what the tool affects. It does not, however, distinguish itself from the close sibling archive_quiz, which likely performs a similar reversible state change.

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 explicit when-to-use guidance, no exclusion, and no named alternative. With archive_quiz among the siblings, an agent is left to guess whether to archive or soft-delete; the description never routes that decision.

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