Skip to main content
Glama

battle_live

Fetch live matches and recent results to track ongoing battle.training ladder and cup activity.

Instructions

Matches running now and the latest results.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and does not meet it. It never says whether the call is read-only (implied but unstated), how 'running now' is determined, how many matches or results come back, whether results are cached or snapshot-at-call-time, or whether any authentication is needed. For a live-data tool the freshness semantics are the single most important thing to disclose and they are absent.

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?

One short sentence with no filler, and the two payload elements (live matches, latest results) are front-loaded. It is efficient, though its brevity reflects under-specification rather than disciplined compression.

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

Completeness2/5

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

Even for a zero-parameter read tool with no output schema, the description leaves critical gaps: it does not define the return shape or quantity, what 'latest' means in time or count, or how live matches are identified. The tool is simple, but 'live' data demands freshness semantics that are entirely 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?

The tool takes zero parameters (empty object schema, required list empty), so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly makes no false claims about filtering options.

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

Purpose3/5

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

The description identifies the subject matter — currently running matches plus the newest results — so an agent can infer this returns a live match feed. But it is a noun phrase with no verb (list/get/fetch) and never distinguishes itself from sibling tools like battle_match, battle_ladder, or battle_replay, which plausibly touch the same data. Purpose is guessable rather than stated.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: no indication of whether this is for polling live state, checking recent outcomes, or something else, and no mention of any alternative tool or precondition. The agent must infer placement in the workflow purely from the name.

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