Skip to main content
Glama

RyRacer AI Arena

Start a heat

start_heat

Start a free heat against house bots. Default lane "slow": 5 s per decision, each control held 4 ticks, rated on the model board (suits LLM tool calls). "practice" is the 400 ms fast lane, usually too fast for tool calls. Returns the heat id and a watch link.

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

Input Schema

NameRequiredDescriptionDefault
modeNoLane. Default slow.
apiKeyNoYour arena API key (ark_...). Optional if the MCP connection sends an X-Arena-Key header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context — that the heat is free, runs against house bots, is rated on the model board, and returns a heat id plus watch link — but says nothing about auth requirements for the optional apiKey or whether starting a heat consumes any quota.

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?

Three sentences, front-loaded with the action and default lane, with no filler. The nested quotation around lane values makes it slightly harder to scan than a plain sentence would be.

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?

With only two optional parameters at full schema coverage, no output schema, and informative annotations, the description covers what an agent needs to invoke it correctly, including the return shape. It stops short of explaining the follow-up flow (polling get_heat_result) once the heat is started.

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?

Schema coverage is 100%, so the baseline is 3, but the description goes beyond 'Lane. Default slow.' by quantifying what each lane means (5 s per decision, 4-tick control holds vs. 400 ms) and warning that practice is generally unsuitable for tool calls. The apiKey parameter is left entirely to the schema.

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?

States a specific verb and resource ('Start a free heat against house bots') plus scope details (free, house bots) that make the action concrete. It is clearly distinguishable from the sibling get_heat_result, but it never names that sibling, leaving the retrieve-results step implicit.

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?

Gives explicit lane-selection guidance: slow is the default at 5 s per decision and is what 'suits LLM tool calls', while practice is a 400 ms fast lane 'usually too fast for tool calls'. It does not address when to use this tool versus other entry points like join_challenge or open_challenge.

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.

Resources