Skip to main content
Glama

Удаление вопроса из избранного

delete_favorite_question
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": {
      "workspace_id": "<workspace_id>",
      "favorite_question_id": "<favorite_question_id>"
    },
    "name": "delete_favorite_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYesID воркспейса (из workspace://list).
favorite_question_idYesID вопроса (из get_favorite_questions).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds genuinely new behavioral context: deletion is scoped to the account library only, and copies of the question inside quizzes are untouched — exactly the fact an agent needs before calling a destructive tool. It stops short of describing error behavior (e.g. deleting a non-existent ID) or why idempotentHint=false matters.

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?

Two short sentences with zero filler; the scope of deletion comes first and the non-obvious side effect second. Every sentence carries information an agent cannot get from the schema or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 with full schema coverage and no output schema, the description covers what is removed and what is preserved. It could still note whether the call fails when the favorite is absent or what is returned, but the essentials for correct invocation are present.

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 both parameters already document their source (workspace://list and get_favorite_questions). The description adds no further meaning about either parameter, 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 names a specific verb and resource: 'Убирает вопрос из библиотеки аккаунта' (removes a question from the account's library). That clearly distinguishes it from quiz-level deletion siblings such as delete_quiz, but it does not explicitly name save_favorite_question or get_favorite_questions as the complementary tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: call this when a question should no longer be in the favorites library. There is no explicit when-not guidance, no mention of the alternative (save_favorite_question), and no statement about preconditions such as whether the question must already exist in the library.

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