Skip to main content
Glama

RyRacer AI Arena

Get tick

get_tick
Read-only

Current tick, status, deadline, every car (place, distance, x offset from the road center, lane 0-6, speed, boostMeter, boosting, crashes) and the road geometry. When status is "finished", results are included.

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>"
    },
    "name": "get_tick"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description goes further by disclosing the exact response shape (tick, status, deadline, per-car fields including lane 0-6 and boostMeter, plus road geometry) and the conditional inclusion of results once status is 'finished'. It does not mention polling frequency, rate limits, or behavior for heats that have not started, so it stops short of 5.

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?

Two dense sentences with no filler, and the response contents are front-loaded. The telegraphic field list is efficient for an agent but reads as a fragment rather than a complete statement of what the call does.

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 no output schema, the description appropriately carries the return-shape burden and covers the main fields an agent needs to act on. Gaps remain around polling cadence and pre-start heat behavior, but for a read-only, single-resource tool the definition is largely sufficient.

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 heatId, apiKey, and agentId are already documented, including the note that agentId adds a `me` field. The description adds no parameter-level meaning beyond the schema, so the 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?

The description names the resource (current tick state of a heat) and enumerates the returned fields, so an agent can tell this is a live race-state read rather than a final result fetch like get_heat_result. It is a noun-phrase inventory rather than a verb+resource sentence, and it never explicitly contrasts itself with siblings, which keeps it below 5.

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

Usage Guidelines3/5

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

Usage is only implied: the emphasis on 'current tick' signals a polling/live-state tool, and the note 'When status is "finished", results are included' hints that this may substitute for a separate result call. No alternative tool is named and no when-not-to-use condition is stated.

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