Skip to main content
Glama

Save a unit loadout

save_unit_loadout
Destructive

Saves a named unit configuration using datasheet and choice ids from get_unit_options. Use a new UUID for a new configuration. Reusing an id keeps the first saved configuration. Use rename_unit_loadout to change its name. 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": {
      "name": "<name>",
      "catalogueId": "<catalogueId>",
      "pick": "<pick>",
      "id": "<id>"
    },
    "name": "save_unit_loadout"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
nameYes
pickYes
joinedNo
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.
catalogueIdYes
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.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true; the description goes beyond them by disclosing the non-overwrite id semantics and the required permission scope, which the agent cannot infer from the schema. It stops short of saying what a save implies for existing saved lists or how deletion relates to delete_unit_loadout, so it is not fully complete on the mutation's blast radius.

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?

Four short sentences, each doing distinct work: purpose, id semantics, renaming alternative, 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.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a complex nested-schema write tool with no output schema and seven parameters, so the description's brevity leaves real gaps: the joined/attached-unit structure, catalogueId, and what a successful save returns or confirms are all unexplained. The behavioral essentials (id semantics, permission, rename routing) are covered, making it adequate but not thorough.

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 29%, so the description must carry weight; it does clarify the id (UUID per configuration) and points at get_unit_options for entryId and choice ids. However it says nothing about catalogueId, the joined array of attached units, or the llm_model and conversation_id telemetry parameters, leaving several required and optional fields unexplained outside the schema.

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 a specific verb and resource ('Saves a named unit configuration') and immediately anchors the inputs to datasheet and choice ids obtained from get_unit_options. It also separates itself from rename_unit_loadout and delete_unit_loadout by naming the renaming path explicitly, so an agent can pick the right sibling without opening another schema.

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

Usage Guidelines5/5

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

Gives explicit conditional guidance: new configurations get a new UUID, reusing an id preserves the first saved configuration, and renaming goes through rename_unit_loadout. The 'Requires mcp:manage' line adds a prerequisite that would otherwise only surface as a runtime failure.

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