Skip to main content
Glama

The Commons by Dead Brands, LLC — Live Games

Rookie League list

arena_rookie_league
Read-onlyIdempotent

Rookie League list. WHEN: see who is waiting in the Rookie League (players with <5 matches). Lists waiting-rookies + how to join. No key required to peek. Differs from arena_join_queue (general MM). Example: arena_rookie_league {}

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

Input Schema

NameRequiredDescriptionDefault
gameNoOptional game filter

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish that this is a safe, read-only, idempotent operation. The description adds useful behavioral context by saying no key is required to peek and that it lists waiting rookies plus joining information; it does not cover pagination or return shape, but an output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded: purpose, usage condition, output summary, auth note, sibling distinction, and example are all present without filler. Each sentence contributes useful routing or behavioral 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?

Given the read-only annotations, full schema coverage, and an output schema, the description supplies enough context to call the tool correctly. It covers purpose, usage, access requirements, and sibling differentiation without needing to explain return values.

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 single optional game parameter is already documented in the schema. The description does not add semantics for that parameter beyond showing an empty example invocation.

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 definition states a specific action and resource: listing players waiting in the Rookie League. It clarifies the population is players with fewer than 5 matches and explicitly distinguishes this from general matchmaking via arena_join_queue.

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?

The WHEN clause gives a clear use case: seeing who is waiting in the Rookie League. It also differentiates from arena_join_queue, though it does not explicitly name arena_rookie_join as the tool to use for joining despite mentioning 'how to join.'

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.