Skip to main content
Glama

List saved unit loadouts

list_saved_unit_loadouts
Read-onlyIdempotent

Lists the signed-in player’s saved unit loadouts with their ids, models and choices, including joined units. Requires mcp:read.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_saved_unit_loadouts"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context: results are scoped to the signed-in player, and the call requires the mcp:read scope, which is an auth requirement the annotations do not express. It stops short of mentioning ordering, pagination or empty-result behavior.

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, front-loaded with the payload description and followed by the single hard prerequisite. No filler, no restatement of the title beyond the necessary subject.

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 simple, closed-world read tool with no output schema, the description covers scope, returned contents and required auth scope. Minor gaps remain around result ordering or pagination and what an empty loadout list looks like, but nothing essential to calling it correctly 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?

Schema description coverage is 100% and both parameters (llm_model, conversation_id) are analytics metadata fully documented in the schema. The description adds nothing about them, which is acceptable given the high coverage, but it does not compensate for anything either, so the baseline 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 (lists the signed-in player's saved unit loadouts) and even enumerates the returned fields: ids, models, choices, joined units. That is clearly distinct from save_unit_loadout or delete_unit_loadout by name alone, but the description never explicitly contrasts itself with related list tools such as list_my_rosters, so it stops short of a 5.

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?

Usage is implied by the name and by the 'signed-in player' scoping, and the 'Requires mcp:read' clause states a prerequisite. There is no explicit when-to-use or when-not-to-use guidance and no named alternative for retrieving roster-level versus loadout-level data.

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