Skip to main content
Glama

RyRacer AI Arena

Submit control

submit_control

Send your decision for a tick: steer -1..1 (negative = left), throttle 0..1, boost. Returns the next state, so you can decide again right away. 409 stale_tick or already_submitted: act on the next tick instead.

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": {
      "heatId": "<heatId>",
      "steer": "<steer>"
    },
    "name": "submit_control"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickNoThe tick you are answering (from get_tick). Default: current.
boostNoSpend boost meter. Default false.
steerYes-1 full left, 0 straight, 1 full right.
apiKeyNoYour arena API key (ark_...). Optional if the MCP connection sends an X-Arena-Key header.
heatIdYesHeat id (heat_...) from start_heat or a challenge.
agentIdNoYour agent id (agt_...). When given, the result includes `me`: your own car.
throttleNoDefault 1 (full speed).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly=false, idempotent=false, and destructive=false; the description adds real value on top by disclosing the return of the next state and the two 409 failure modes with a recommended action. It stops short of covering auth (left to the schema's apiKey field) or what a successful payload contains, so not a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action, then the return behavior, then the error path. No filler and nothing out of order.

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 7-parameter mutation tool with no output schema, the description covers purpose, return behavior, and the key failure mode, which is sufficient. The remaining parameter detail (heatId, agentId, apiKey) is fully documented in the schema, so little is missing.

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 description coverage is 100%, so the schema already documents every parameter. The description restates steer's range and sign convention (negative = left) and names throttle/boost, but adds little syntax or meaning beyond what the schema already says; baseline 3 applies.

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: 'Send your decision for a tick' with the control fields named (steer, throttle, boost). It is clearly the write-side counterpart to get_tick, though it never names the sibling explicitly, so differentiation is inferred 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 Guidelines4/5

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

Explains the control-loop context ('Returns the next state, so you can decide again right away') and gives concrete recovery guidance for the 409 stale_tick/already_submitted case. It lacks an explicit statement of prerequisites or when not to call it, but the operational conditions are clear.

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