Skip to main content
Glama

Delete a kit piece

delete_kit_piece
DestructiveIdempotent

Remove an outfit, place or prop A plan that used it can’t be made any more: plan again.

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": {
      "kit_id": "<kit_id>"
    },
    "name": "delete_kit_piece"
  }
}

Input Schema

NameRequiredDescriptionDefault
kit_idYesThe kit piece id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/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 covered. The description nonetheless adds real context beyond them: deleting a piece invalidates any plan that referenced it, and the user must re-plan. That cascade effect is the kind of downstream impact annotations cannot express.

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

Conciseness3/5

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

Very short, but two unrelated thoughts are jammed into one unpunctuated string, and the second clause is garbled ('A plan that used it can't be made any more'). The consequence information is worth keeping; the phrasing costs comprehension.

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 delete with no output schema, the definition covers the resource, the destructive nature (via annotations) and the downstream plan impact. It never states whether the deletion is recoverable, which is the one gap an agent might still need.

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, and the schema documents it fully ('The kit piece id', with min/max length), giving the 100%-coverage baseline of 3. The description adds nothing about id format or where to obtain a valid kit_id.

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 verb 'Remove' plus the concrete kit-piece kinds ('outfit, place or prop') make clear exactly which resource this deletes, distinguishing it from delete_look, delete_video and delete_artist_photo. It stops short of naming a sibling explicitly, and the missing punctuation turns the sentence into a run-on.

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?

There is no statement of when to choose this over update_kit_piece or archive_* alternatives, and no prerequisites. The closing note about plans is a consequence, not routing guidance for the call itself.

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