Skip to main content
Glama

Blends Delete

blends_delete
Destructive

Remove blends from a report with conflict-checked, journalled writes. Deletion is refused while components or filters still reference a blend and can be undone via operation_restore.

Instructions

Remove blends from the report (Manage blends > Remove). Refused while a component, filter or other resource still references a blend. One journalled report write, restorable with operation_restore.

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": {
      "blend_ids": "<blend_ids>",
      "expected_report_content_fingerprint": "<expected_report_content_fingerprint>"
    },
    "name": "blends_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
blend_idsYes
report_idNo
expected_report_content_fingerprintYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare destructive=true and readOnly=false, so the safety profile is covered; beyond that, the description adds genuinely new behavior: the reference-integrity precondition that causes a refusal, that the operation is a single journalled report write, and that it is reversible via operation_restore. These are exactly the traits an agent cannot infer from the schema or annotations.

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?

Three short sentences, ordered from what it does to the failure condition to the durability/recovery guarantee, with no filler. The critical constraint is front-loaded rather than buried.

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?

The presence of an output schema means return values need not be described, and the destructive-write behavior plus recoverability is well covered. However, for a destructive tool whose dry_run parameter defaults to true, omitting any mention of the preview gate and the required content fingerprint leaves a material gap for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden, yet it names no parameters at all. Critically, it never mentions that dry_run defaults to true, so an agent could believe it has deleted blends when it only ran a preview, and it says nothing about expected_report_content_fingerprint or report_id. Only the plural 'blends' hints at the blend_ids array.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource, 'Remove blends from the report', and even anchors it to the UI path (Manage blends > Remove). That is unambiguous enough to separate it from siblings such as blends_rename, blends_list, or components_delete.

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

Usage Guidelines4/5

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

It states the blocking precondition ('Refused while a component, filter or other resource still references a blend') and names the recovery path ('restorable with operation_restore'), which tells an agent both when the call will fail and what to do afterwards. It gives no explicit when-not or triggering-context guidance, but the deletion intent is clear from the name and verb.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools