Skip to main content
Glama

battle_meta

Fetch draft meta for an armor or sub theater to compare drafted squads by pick and win rate, supporting strategic lineup choices.

Instructions

Draft meta for a theater: the most drafted squads with pick and win rate.

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_meta"
  }
}

Input Schema

NameRequiredDescriptionDefault
theaterNoarmor

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 burden. It implies a read-only stats lookup and names the metrics returned, but says nothing about data freshness, aggregation window, sample size, ordering, or rate limits.

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?

A single front-loaded sentence with no filler; the resource and its payload are stated up front. It is arguably too terse for a tool whose only parameter value is opaque.

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?

With no output schema, the description usefully enumerates the returned fields (squads, pick rate, win rate), which is the right compensation. It still leaves the theater enum and result ordering/freshness unexplained, so it is adequate but not complete.

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 0%, so the description is the only place that connects the parameter to the concept of a 'theater'. However, it does not explain the enum values 'armor' and 'sub' or that the parameter defaults to 'armor', leaving the key semantic ambiguity unresolved.

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 resource (draft meta for a theater) and states exactly what is returned: the most drafted squads with pick and win rate. That distinguishes it from siblings like battle_ladder or battle_cup, though the description never explicitly contrasts with them.

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 guidance on when to use this versus alternatives (e.g. ladder standings or cup data), and no prerequisites or exclusions. The implicit usage — look up popular picks and win rates — must be inferred from the noun phrase alone.

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