Skip to main content
Glama

Read my model collection

get_my_collection
Read-onlyIdempotent

Returns the models the signed-in player owns, as their collection page keeps them, grouped by faction. Each entry's id and slug are the datasheet's, the same as list_units gives, with the models owned, how many are built and painted, and countsAs: other datasheets the player says those models can also be fielded as. A datasheet the current army data no longer has is named "A datasheet from earlier rules". Pass faction to read one army; a collection of more than 200 datasheets without one returns only each faction's totals. 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_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
factionNoFaction id, URL slug, or display name, as list_factions gives them.
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. 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
Behavior3/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description still adds real behavioral context the annotations don't: the mcp:read authorization requirement, the >200-datasheet truncation to faction totals, and the 'A datasheet from earlier rules' placeholder for stale entries.

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?

It is dense but front-loaded with the core purpose, then return shape, then edge cases and auth. Every sentence carries content, though the packed commas make the entry-field enumeration hard to parse on first read.

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 return-shape burden and does so — naming owned counts, built/painted counts, countsAs aliasing, and the missing-datasheet fallback — plus truncation behavior and permissions. Nothing an agent needs to call this correctly is missing.

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?

With 100% schema coverage the baseline is 3, and the description genuinely goes beyond the schema by explaining what passing faction actually scopes ('read one army') and that omitting it on a large collection collapses the result to faction totals — semantics absent from the schema's one-line faction description.

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 opens with a specific verb and resource — 'Returns the models the signed-in player owns ... grouped by faction' — and ties the entry ids back to list_units, so an agent knows the identity space is shared with that sibling while the resource (owned collection vs. unit catalog) is distinct.

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 operational guidance: 'Pass faction to read one army' and the threshold rule that an unfiltered collection over 200 datasheets returns only per-faction totals. What's missing is any explicit statement of when to prefer this over a sibling such as list_my_rosters, but the usage conditions it does state are clear and actionable.

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