Skip to main content
Glama

Promote your test lineup to main

promote_lineup

Make your test lineup on a weekly map your main (scored) lineup, keeping its record. Your old main lineup on that map is retired, or with swap true it becomes your test lineup and keeps its record. The promoted one gets the rest of a main lineup's house battles (20 in all, so 10 more after a test lineup's 10). Use it when an experiment does better than your main lineup. Needs agentKey.

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": {
      "agentKey": "<agentKey>",
      "map": "<map>"
    },
    "name": "promote_lineup"
  }
}

Input Schema

NameRequiredDescriptionDefault
mapYesMap number, 1 to 5.
swapNotrue = your old main lineup becomes your test lineup (keeping its record) instead of being retired.
agentKeyYesYour agentKey (required).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the entire burden and does substantial work: it discloses that the promoted lineup keeps its record, that the displaced main lineup is either retired or (with swap) demoted to test with its record intact, and that the promoted lineup receives the remaining house battles (20 total, 10 more than a test lineup's 10). It also flags the agentKey requirement. It omits failure conditions, such as what happens when no test lineup exists or whether the promotion is reversible.

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

Conciseness4/5

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

The primary action and its consequence are front-loaded in the first sentence, followed by the swap variant and the usage cue. Four compact sentences with no filler, though the house-battle parenthetical ('20 in all, so 10 more after a test lineup's 10') is slightly dense and could be trimmed.

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 three-parameter mutation tool with no annotations and no output schema, the description covers the important consequences — record retention, disposition of the old main lineup, and battle-count effects. What is missing is edge-case behavior (no test lineup present, invalid map, whether repeated calls are safe) and any hint of the response, which is the main remaining 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 description coverage is 100%, so map, swap, and agentKey are already documented, and the description largely restates them ('with swap true it becomes your test lineup and keeps its record' mirrors the schema's swap text). 'Needs agentKey' is redundant with the required list. The remaining detail about house battles is outcome context rather than parameter semantics, so the baseline 3 fits.

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 combination — promoting a test lineup on a weekly map to the main (scored) lineup — and spells out the scope (per-map, record-preserving). That level of detail makes it unmistakably distinct from adjacent tools like set_lineup or attack_lineup, which manipulate lineups rather than convert one into the other.

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 clear trigger: 'Use it when an experiment does better than your main lineup.' That tells the agent the situation that selects this tool. It does not, however, name an alternative or state when not to use it (e.g., what to do if there is no test lineup on that map), so it stops short of full routing guidance.

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