Skip to main content
Glama

Удаление набора оформления

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

Input Schema

NameRequiredDescriptionDefault
preset_idYesID набора (из get_workspace_report_appearance).
workspace_idYesID воркспейса (из workspace://list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 carried by structured data. The description nonetheless adds a genuinely useful non-obvious behavior: surveys that had the preset applied keep their appearance, so deletion does not cascade. It says nothing about irreversibility or whether a preset in active use can be deleted, which for a destructive tool is a remaining gap.

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?

Two compact sentences with the action stated first and the side effect second; every clause earns its place. Sizing is appropriate for a two-parameter action tool with no output schema.

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 destructive tool whose safety hints are already supplied by annotations and whose two parameters are fully documented, the description covers the essential behavior including the non-cascade effect on surveys. Only the absence of any note on reversibility or preconditions keeps it from being fully complete.

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 coverage is 100% and both parameters carry their own descriptions including provenance (preset_id from get_workspace_report_appearance, workspace_id from workspace://list). The description adds no additional meaning about parameter formats, ranges or scoping, 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 gives a concrete verb plus resource — 'Удаляет набор оформления из библиотеки аккаунта' — which is unambiguous and identifies exactly what is removed and from where. It does not name a contrasting sibling (e.g. create_report_appearance_preset), so it stops just short of the top score, but the purpose is never in doubt.

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 only implied by the action itself: an agent can infer this is the tool for removing a stored appearance preset. There is no explicit statement of when to delete versus update a palette, nor any precondition such as whether the preset must be unused before removal, which matters for a destructive sibling set like this one.

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