Skip to main content
Glama

List tournament-winning lists

list_winning_lists
Read-onlyIdempotent

Lists a faction's top-four tournament placings from 40k Stats and Mini Headquarters whose lists import cleanly and are legal under today's army data, newest first; pass includeNoLongerLegal for lists a points or rules change has made illegal too, such as to read the meta from before a points rise. A faction counts its whole family, so a list imported under an earlier rules version still counts. of is how many lists matched and events the date range of their events; a small of is a small sample. latestUpdate is the date of the faction's newest points or datasheet update and sinceLatestUpdate how many lists come from events since; lists from before it were built for other points, so weigh them less or pass since. detachments counts how many lists took each detachment. battleSizes counts the faction's lists at each size: when it has none at the size being built, say so, and read other sizes' lists as which units the faction favours rather than as a shape to copy. datasheets names every datasheet those lists field with how many of them field it, most first, and the unit sizes taken, most common first. Each list gives its placing, record, event, detachments, Force disposition, points under today's data and as the player reported them, whether it is legal today, and units with every copy's model count; pass its id to get_winning_list for the full list as a draft. A placing reflects the player and the field as much as the list: learn the shapes and staples these lists share rather than copying one. While checking is true the first import is still running and every count is partial; say so.

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": {
      "faction": "<faction>"
    },
    "name": "list_winning_lists"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoHow many of the newest matching lists to return in full.
sinceNoOnly placings from events on or after this date (YYYY-MM-DD), such as the latestUpdate an earlier call returned.
factionYesFaction id, URL slug, or display name from list_reference or list_units.
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.
battleSizeNoOnly placings at this battle size in points, such as 2000.
detachmentNoDetachment id, slug, or name from list_units, to list only placings that took it.
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.
includeNoLongerLegalNoAlso list placings that import cleanly but break today’s points or rules, marked legalToday false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / includeNoLongerLegal
      Added value: +{
      +  "default": false,
      +  "description": "Also list placings that import cleanly but break today’s points or rules, marked legalToday false.",
      +  "type": "boolean"
      +}
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/closed-world, yet the description adds substantial behavior: legality is judged against today's army data, faction family aggregation across earlier rules versions, 'a small of is a small sample', and the crucial partial-results caveat 'While checking is true the first import is still running and every count is partial; say so.' It also warns that a placing reflects the player and field, not just the list.

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

Conciseness3/5

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

The purpose and the key caveats are front-loaded, but the body is one long semicolon-chained run-on that mixes return-field documentation, meta-analysis advice, and flag guidance without paragraph or list structure. No output schema exists so the return detail earns its place, but it could be far easier to scan.

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?

With no output schema, the description carries the return-shape burden and does so thoroughly: of, events, latestUpdate, sinceLatestUpdate, detachments, battleSizes, datasheets, and per-list fields including legality and points under today's data. The main gaps are that it never states the count/pagination relationship explicitly (what of means versus count) or what an empty result implies beyond the battle-size note.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: since is tied to 'the latestUpdate an earlier call returned', includeNoLongerLegal is tied to the 'legalToday false' marker and a use case, and count is framed as 'how many of the newest matching lists'. The remaining params (faction, battleSize, detachment, llm_model, conversation_id) are left entirely to 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?

The opening clause gives a precise verb, resource, scope and ordering: 'Lists a faction's top-four tournament placings from 40k Stats and Mini Headquarters ... newest first', plus the legality filter. It also names the sibling that goes deeper ('pass its id to get_winning_list for the full list as a draft'), so the agent can distinguish it from get_winning_list without opening a 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 concrete when-to-use guidance for the optional flags: pass includeNoLongerLegal 'to read the meta from before a points rise', and pass since because lists from before latestUpdate 'were built for other points, so weigh them less'. It also advises how to interpret results across battle sizes. It stops short of explicit exclusion rules against the other list_* siblings, so not a 5.

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