Skip to main content
Glama
Sign In

GoodBarber

by dev.goodbarber
OverviewDiscussionsAdmin

Delete option

shop_delete_option
Destructive

Deletes a specific variant option. Once an option gets used on a product, it cannot be deleted, even if the product is deleted. Guidance: Deletes a specific variant option. WARNING: Once an option gets used on a product, it cannot be deleted, even if the... | context: option_id

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": {
      "option_id": "<option_id>"
    },
    "name": "shop_delete_option"
  }
}

Input Schema

NameRequiredDescriptionDefault
option_idYesOption Unique ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Adds a meaningful behavioral constraint: options that have been used on a product cannot be deleted, even if the product is deleted. This goes beyond the destructiveHint annotation.

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

Conciseness2/5

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

The description is repetitive, with the main sentence duplicated under 'Guidance' and the warning repeated. The trailing '| context: option_id' is unstructured and unclear.

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?

Covers the crucial deletion constraint but lacks details on success/failure behavior, existence checks, or any side effects. Adequate for a simple delete operation but not comprehensive.

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?

The single parameter option_id is already well-described in the schema as 'Option Unique ID', and the description adds no additional semantic detail.

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?

States clearly that it deletes a specific variant option, distinguishing it from sibling tools like shop_delete_variant or shop_delete_product.

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?

Provides no explicit guidance on when to use this tool vs alternatives such as shop_update_option or shop_delete_variant. The warning about usage constraints is helpful but not a usage guideline.

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

All GoodBarber toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources