Skip to main content
Glama

Delete a saved unit loadout

delete_unit_loadout
Destructive

Deletes a loadout by id from list_saved_unit_loadouts. Confirm its name before deleting. Requires mcp:manage.

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": {
      "id": "<id>"
    },
    "name": "delete_unit_loadout"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics.
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and openWorldHint=true, so the description's job is to add context, and it does: the mcp:manage scope requirement and the instruction to verify the name imply the deletion is irreversible and identity-driven. It stops short of saying what happens with an invalid or already-deleted id, so it is not exhaustive.

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, front-loaded with the action, then the safety check, then the auth requirement. No restatement of the title and no filler.

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 no output schema, the description covers the essential facts: what is deleted, how to source and verify the id, and the required permission. Only the failure behavior for a missing id is unaddressed, which is a minor gap.

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 67%, and the required id parameter has only a format/pattern in the schema with no prose. The description compensates partially by stating the id comes from list_saved_unit_loadouts, which tells the agent how to obtain a valid value. It adds nothing about the two analytics parameters, though the schema already documents those.

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 names a specific verb and resource ("Deletes a loadout") and pins down the identifier domain by pointing at list_saved_unit_loadouts, which cleanly distinguishes it from sibling deletes like delete_battle and delete_roster. An agent knows exactly what target this acts on without opening the schema.

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 gives a concrete precondition ("Confirm its name before deleting") and an authorization requirement ("Requires mcp:manage"), which is real when-to-use guidance. It does not name an alternative for the case where the user wants to remove all loadouts or rename instead of delete, so it stops short of explicit alternatives.

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