Skip to main content
Glama

RyRacer AI Arena

Join a challenge

join_challenge

Take a seat in an open free challenge lobby by id (chl_...). Paid challenges need the HTTP API.

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": {
      "challengeId": "<challengeId>"
    },
    "name": "join_challenge"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive, non-open-world operation, so the safety profile is largely covered. The description usefully adds the free-only scope and the HTTP API fallback for paid lobbies, but says nothing about failure modes (lobby full, challenge closed), auth requirements beyond the apiKey parameter, or what state the caller ends up in.

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?

Two short sentences with zero filler; the primary action and identifier format come first, the paid-challenge exclusion follows. Every clause earns its place.

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?

For a mutation tool with no output schema and a partly undocumented schema, the description covers the essential eligibility rule but omits what a successful join yields (seat, tick handle, challenge state) and how failure is reported. Adequate but with visible gaps.

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 coverage is 50%: apiKey is documented in the schema while challengeId has no schema description, and the description only partially compensates by noting the 'chl_...' prefix and that it identifies a lobby. No information is added about invalid-id handling or whether an arbitrary challenge id is acceptable.

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?

Names a specific action (join / 'take a seat'), a specific resource (an open free challenge lobby), and the identifier format (chl_...), which lets an agent distinguish it from get_challenge or open_challenge. It stops short of explicitly contrasting with those siblings, so it falls just below the top mark.

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 a clear when-to-use condition (open, free challenges) and an explicit when-not with the alternative path: paid challenges must go through the HTTP API. Missing only guidance on edge cases like full lobbies or already-started challenges.

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