Skip to main content
Glama

List battlefields for a tournament table

list_tournament_table_battlefields
Read-onlyIdempotent

Lists the allowed deployments and terrain layouts after the table’s rosters are revealed. Use the event token, round and table from get_my_event. Requires mcp:read.

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": {
      "token": "<token>",
      "round": "<round>",
      "table": "<table>",
      "missionPackId": "<missionPackId>"
    },
    "name": "list_tournament_table_battlefields"
  }
}

Input Schema

NameRequiredDescriptionDefault
roundYes
tableYes
tokenYes
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.
eventTokenNo
missionPackIdYes
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

A3.6/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 bar is lower; the description still adds the auth scope ('Requires mcp:read') and the read-availability precondition. It does not describe ordering, pagination, or what an empty result means, which keeps it below a 5.

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 sentences with no padding, and the core function is front-loaded ahead of the sourcing and permission details. Nothing here is filler, though a slightly tighter phrasing of the preconditions was possible.

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

Completeness3/5

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

For a seven-parameter tool with no output schema, the description leaves the required missionPackId unaddressed and says nothing about the shape or ordering of the returned deployment/terrain list. The auth and precondition notes are valuable, but the definition is not fully self-sufficient.

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?

Only 29% of the schema carries descriptions, and the description compensates partially by tying token, round and table to get_my_event. The required missionPackId is unexplained in both schema and description, and the description's mention of a single 'event token' does not disambiguate the separate 'token' and 'eventToken' fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource — 'Lists the allowed deployments and terrain layouts' — and adds the precondition that rosters must already be revealed. An agent can distinguish this read from the sibling mutator set_tournament_table_battlefield, though that sibling is never named explicitly.

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

Usage Guidelines3/5

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

Provides a useful sourcing instruction ('use the event token, round and table from get_my_event') and a timing condition ('after the table's rosters are revealed'). It stops short of saying when to prefer this over alternatives or what to do if rosters are not yet revealed.

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