Skip to main content
Glama

Rename a saved unit loadout

rename_unit_loadout
Destructive

Renames a loadout by id from list_saved_unit_loadouts. 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": "<name>"
    },
    "name": "rename_unit_loadout"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
nameYes
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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true; the description is consistent with them and adds the scope/auth requirement, which is genuine extra context. However, for a tool flagged destructive it never explains what is lost — e.g. whether the previous name is overwritten irrecoverably — leaving the most important behavioral trait to the annotation alone.

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?

Two short sentences, no filler, with the operation stated first and the permission prerequisite second. Every phrase carries information.

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?

For a destructive mutation with no output schema, the definition covers the permission gate and id provenance but omits failure behavior, whether the old name is recoverable, and any return/confirmation detail. It is adequate to call the tool, not complete enough to predict the outcome.

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 only 50%: llm_model and conversation_id are documented in the schema, while id and name are not. The description partially compensates by explaining that id is a loadout id from list_saved_unit_loadouts, but adds nothing about the name parameter's constraints (1-80 chars) or about the two analytics parameters.

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 description names a specific verb and resource ('Renames a loadout') and pins the target by noting the id comes from list_saved_unit_loadouts, which distinguishes it from save_unit_loadout and delete_unit_loadout. It stops short of naming those siblings explicitly, so it is clear rather than exemplary.

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

Usage Guidelines3/5

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

It gives a real prerequisite ('Requires mcp:manage') and tells the agent where to obtain the id, which is useful routing. It does not state when to prefer this over save_unit_loadout (which could plausibly also change a name) or what happens if the loadout does not exist.

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