Skip to main content
Glama

Управление темами оформления

manage_theme
Destructive

Наводит порядок в темах оформления: делает копию темы, чтобы не переписывать её с нуля, удаляет ненужную и возвращает удалённую. Опросы, которые пользовались удалённой темой, переводятся на тему по умолчанию — иначе опубликованный опрос сломался бы. Список тем — в theme://list.

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>",
      "action": "<action>",
      "theme_id": "<theme_id>"
    },
    "name": "manage_theme"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesЧто сделать: copy — копия темы, delete — удалить, restore — вернуть удалённую.
theme_idYesID темы из theme://list.
workspace_idYesID workspace. Взять из workspace://list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 still earns credit by disclosing a non-obvious side effect not in the schema or annotations: quizzes using a deleted theme are moved to the default theme. It does not address whether restore has a time limit or whether deletion is final, which keeps it below 5.

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?

Three tight sentences front-loaded with the resource and the operation list, followed by the consequence and the resource pointer. The clause 'иначе опубликованный опрос сломался бы' is rationale rather than information, marginally over-explaining but still short and readable.

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 3-parameter mutation tool with no output schema, the definition covers what the actions do, the destructive side effect, and where to obtain IDs. Missing only edge-case behavior (restore window, whether delete is reversible at all, error on invalid theme_id).

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 every parameter including the action enum is documented in the schema with the same wording as the description. The description only repeats the theme://list pointer already present in the theme_id schema field, adding no new meaning (e.g. what happens if action=restore targets a theme that was never deleted). 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 resource (themes) and enumerates the three operations precisely: copy, delete, restore ('делает копию темы... удаляет ненужную и возвращает удалённую'). An agent knows exactly what the tool does. It stops short of a 5 because it never distinguishes these operations from the nearby create_theme / update_theme / apply_quiz_theme siblings, leaving the copy-vs-create boundary implicit.

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 by the action set and by the motivation given for copy ('чтобы не переписывать её с нуля'), but there is no explicit when-to-use / when-not and no named alternative tool — e.g. nothing tells the agent to prefer create_theme when no source theme exists. The delete guidance is the strongest part, since it warns about downstream effects.

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