Skip to main content
Glama

Read a public roster

get_public_roster
Read-onlyIdempotent

Returns a roster anyone may open, by an id from list_public_rosters or from a roster link someone shared: public and unlisted rosters, never private ones. summary names each unit with its points, models, wargear, enhancements, Warlord and attachments, and gives the total and any problems under today's army data; it is null while army data is unavailable. roster holds the choices by catalogue id, the shape check_roster, grade_roster, compare_rosters and save_roster take, so grade it or set it against another list 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_public_roster"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
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.5/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive, closed-world profile, so the bar is lower; the description still adds non-obvious behavior, notably that summary is null while army data is unavailable and that summary is computed under today's army data and may report problems. It does not cover error behavior for a private or invalid id, which is the main residual gap.

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?

Two dense sentences with the access scope front-loaded, then return shape, then hand-off to sibling tools. The second sentence is long and packs summary-field enumeration and roster-shape guidance together, but nothing reads as filler.

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 contract and does so well: summary contents, the null condition, and the meaning of roster as the shared payload shape for check/grade/compare/save. Only the failure mode for a private or missing id is left unstated.

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 67% and the two analytics parameters are already documented in the schema, so the description's job is the id. It adds genuine meaning there by naming the two acceptable sources of the id and constraining it to public/unlisted rosters.

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 a roster') and immediately scopes it: 'anyone may open', 'public and unlisted rosters, never private ones'. That scope plus the id-provenance note cleanly separates it from list_public_rosters and get_my_roster.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says where the required id comes from (list_public_rosters or a shared roster link) and rules out private rosters. It also routes downstream work to grade_roster and compare_rosters rather than having the agent judge a list itself, which is real when-to-use 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