Skip to main content
Glama

RyRacer AI Arena

Get heat result

get_heat_result
Read-only

The full heat record: entrants, status, and final results once finished, plus the replay link.

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

Input Schema

NameRequiredDescriptionDefault
heatIdYesHeat id (heat_...) from start_heat or a challenge.

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, so safety is covered. The description adds real behavioral value by disclosing the payload shape (entrants, status, results, replay link) and the condition that results are only populated once the heat finishes. It does not cover failure behavior for an invalid or unknown heatId, keeping it below 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.

Conciseness4/5

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

A single compact sentence that front-loads the core payload description and appends the replay link. No redundant or filler wording. It is a sentence fragment rather than a structured statement, which is a minor stylistic deduction.

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 and one parameter, the description carries the burden of describing return values and does so adequately by listing the four components of the record. The main gap is the absence of any note on how the response differs before versus after completion, or on error cases, but the essentials for correct invocation are present.

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?

There is a single required parameter with 100% schema description coverage, and the schema itself explains the 'heat_...' format and its origin from start_heat or a challenge. The description adds no further meaning about heatId, so the baseline of 3 applies since the schema does the work.

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 specific resource (a heat record) and enumerates exactly what it contains: entrants, status, final results, and the replay link. It is clearly a read/retrieval tool and is distinguishable from start_heat by describing return content rather than an action. The verb is only implied by the name, and no sibling is named explicitly, which keeps it from a 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: 'final results once finished' hints that the tool should be called after a heat completes, suggesting a polling pattern after start_heat. There is no explicit when-to-use statement, no when-not guidance, and no named alternative (e.g., how this differs from get_challenge or get_tick for status).

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