Skip to main content
Glama

Read a tournament-winning list

get_winning_list
Read-onlyIdempotent

Reads one top-four tournament placing from list_winning_lists as it imports under today's army data: its placing, whether it is legal today, record and event, the army text the player submitted, draft (the list in the shape check_roster, grade_roster, compare_rosters and save_roster take) and summary, which names each unit with its points, models, wargear, enhancements, Warlord and attachments. Grade the draft with grade_roster or set it against another list with compare_rosters rather than judging it yourself.

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": "get_winning_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesA list id from list_winning_lists.
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

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely non-obvious context beyond them: the record is normalized 'as it imports under today's army data,' includes a legality flag, and returns both raw army text and a normalized draft in a specific schema shape.

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?

A single long sentence, but it is front-loaded with the action and then enumerates returned fields in a readable order. The closing routing sentence is short and earns its place; the field enumeration is dense but each item adds information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

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

There is no output schema, so the description carries the return-value burden, and it does so thoroughly: placing, legality, record and event, army text, draft (with a note that it matches the shape used by check_roster/grade_roster/compare_rosters/save_roster), and summary contents. That is enough for an agent to consume the result correctly.

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 100%, so the id, llm_model and conversation_id are already documented in the schema. The description only echoes that the id comes from list_winning_lists and adds nothing about the analytics parameters; baseline 3 applies.

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: reads one top-four tournament placing out of list_winning_lists. It clearly distinguishes itself from the sibling list_winning_lists (which lists them) and from grade_roster/compare_rosters by describing the detail payload it returns.

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?

Explicitly routes downstream work: 'Grade the draft with grade_roster or set it against another list with compare_rosters rather than judging it yourself,' and the schema ties the id back to list_winning_lists. It never spells out the fetch flow (list first, then get) in prose, but the context makes it clear.

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