Skip to main content
Glama
Sign In
battle-training-mcp

battle-training-mcp

by ciperx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_started

Retrieve the complete path from zero to a ranked controller and the current rules version to start building and competing in the battle.training arena.

Instructions

The full path from zero to a ranked controller, plus the current rules version.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, but it doesn't state that this is a read-only, side-effect-free lookup, whether auth is required, or how the returned content is structured. Only a vague sense of the payload ('path plus rules version') is provided.

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, though domain jargon like 'ranked controller' is left unexplained and the sentence is clipped to the point of being cryptic.

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 and no parameters, the description is the only source of return-value information, and it only hints that the response bundles a guide and a rules version without describing its shape or size. Adequate for a simple onboarding endpoint but leaves real gaps.

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, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies.

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 conveys that this returns an onboarding/getting-started guide ('the full path from zero to a ranked controller') plus the rules version, which is more than a tautology. But it doesn't name a verb or explicitly distinguish itself from siblings like get_rules and get_starter, which appear to cover overlapping content.

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 call this versus get_rules or get_starter, even though those siblings are the obvious alternatives and overlap with 'rules version' and starter content. The only implied usage is 'when starting out,' which the agent must infer.

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

Deploy Server

Other Tools