Skip to main content
Glama

battle_cup

Fetch cup and sponsored-ladder standings by slug, showing prize assignments and recent matches for the specified battle.training ladder.

Instructions

Cup / sponsored-ladder standings by slug (e.g. promotedby-cup-nov-2026). Includes prize assignment and recent matches.

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": {
      "slug": "<slug>"
    },
    "name": "battle_cup"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesLadder slug, e.g. promotedby-cup-nov-2026

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It does disclose the interesting behavioral detail that the response bundles prize assignment and recent matches alongside standings, but says nothing about read-only semantics, auth requirements, pagination, or error behavior for a nonexistent slug.

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 tight sentences, front-loaded with the resource and key, then the payload contents. Minor waste in repeating the slug example that the schema already provides.

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?

For a one-parameter read lookup with no output schema, the description covers what the tool retrieves and what extra data comes back, which is most of what an agent needs. Gaps around error behavior for invalid slugs and response size are small at this complexity level.

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% and the single slug parameter already carries the example 'promotedby-cup-nov-2026'; the description only restates that example. Baseline 3 applies since the schema does the heavy lifting and the description adds no new semantics such as slug casing or format constraints.

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?

The description names a specific resource ('Cup / sponsored-ladder standings') and the lookup key ('by slug'), plus the payload contents (prize assignment, recent matches). It is clear what the tool returns, though it never explicitly contrasts itself with the sibling battle_ladder, which reads as a similar standings tool.

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?

Usage is only implied: an agent can infer this is the tool for cup/sponsored-ladder standings, but there is no statement of when to prefer it over battle_ladder or battle_match, and no note about required slug formats beyond the example or what happens with an unknown slug.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.