Skip to main content
Glama

Read my battle statistics

get_my_stats
Read-onlyIdempotent

Returns the signed-in player's record as their profile shows it, over their latest 200 finished battles except practice games, optionally narrowed. record: battles, won, lost, drawn, rate (win rate 0 to 1, a draw counting half), going first and second, average points, streaks, command points, stratagems and secondary cards used, primary missions, opposing factions and opponents. performance: the same split per detachment, primary mission and battle size. facets: the values each filter takes, with battle counts. rankings: leaderboard places from rated public battles, overall and per faction, unaffected by the filters. List the battles themselves with list_my_battles. 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": "get_my_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoA battle size in points, such as 2000.
factionNoA faction slug you fielded, from facets.factions or list_factions.
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.
detachmentNoA detachment name you fielded, exactly as facets.detachments lists it.
opponentIdNoAn opponent player id from facets.opponents.
missionPackIdNoA mission pack id from facets.missionPacks.
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.
opponentFactionNoA faction slug an opponent fielded, from facets.opponentFactions.
opponentDetachmentNoA detachment name an opponent fielded, from facets.opponentDetachments.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "The 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.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "The 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.",
      +  "type": "string"
      +}
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: the 200-battle cap, exclusion of practice games, the fact that rankings ignore the filters, and the mcp:read scope requirement.

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?

Front-loaded with the core behavior and scope, then a compact enumeration of return sections. The field list is dense and slightly run-on, but each clause carries information an agent needs, so little is wasted.

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?

With no output schema, the description carries the burden of describing return values and does so thoroughly via the record/performance/facets/rankings breakdown. Scope, filter behavior, auth requirement and the sibling alternative are all present, leaving nothing essential missing for a 9-parameter read tool.

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 every parameter is already documented, including where to source valid values (facets.factions, facets.opponents, etc.). The description only adds that filters narrow the result and that facets supplies the filter values, which is marginal beyond the schema, so 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 (returns the signed-in player's record) plus the exact scope: latest 200 finished battles, practice games excluded, optionally narrowed. It then enumerates the four result sections (record, performance, facets, rankings), so an agent knows precisely what it gets and how it differs from list_my_battles.

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 battle-level listing to list_my_battles and states the mcp:read requirement, giving clear context for when to call this instead. It does not spell out when-not-to-use beyond that single alternative, so it falls short of a full 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