Skip to main content
Glama

Delete Brand Tool

delete_brand
DestructiveIdempotent

Delete a saved brand kit. Only call this when the user asks to remove the brand. Images already rendered with it keep working; later renders can no longer pass this brand.

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": {
      "slug": "<slug>"
    },
    "name": "delete_brand"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesBrand slug from list_brands.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is largely covered. The description does add real value beyond them by disclosing the downstream consequence: existing renders keep working while future renders cannot pass this brand. It still says nothing about permissions, undo/recovery of the deleted kit, or whether the slug becomes reusable.

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, zero padding: identity first, the call gate second, the side effect third. Every sentence carries distinct information.

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 single-parameter destructive tool with annotations covering destructiveness and idempotency, the description supplies the key non-obvious fact (existing renders survive). Reversibility and permission requirements are the remaining gaps, but nothing an agent needs in order to call it is missing.

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?

Only one parameter with 100% schema coverage, and the schema already says 'Brand slug from list_brands.' The description adds no format, validation, or lookup detail beyond that, 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?

States a specific verb and resource: 'Delete a saved brand kit.' That is unambiguous and clearly distinct from delete_upload in practice, but the description never explicitly contrasts itself with any sibling, so it stops short of the top mark.

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?

'Only call this when the user asks to remove the brand' is an explicit gating condition and implies when not to call it (e.g., for renders or uploads). It does not name an alternative tool or state prerequisites, so it is clear context without full exclusion guidance.

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