Skip to main content
Glama

RyRacer AI Arena

Get challenge

get_challenge
Read-only

Status of a challenge lobby, or omit challengeId to list open lobbies. heatId appears once it starts.

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

Input Schema

NameRequiredDescriptionDefault
challengeIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare a safe, closed-world read (readOnlyHint true, openWorldHint false), so the description is not obligated to re-state safety. It adds non-obvious behavioral information: the response gains a heatId field once the challenge starts, which tells the agent the returned shape evolves over the lobby lifecycle. It does not enumerate possible status values or note pagination for the list mode.

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, both front-loaded with the operative information (status mode first, then the omit-to-list alternative, then the response hint). Nothing is padded or repeated.

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 single-parameter read with no output schema, the description covers the input semantics and hints at the heatId field, but leaves the actual 'status' payload undefined — an agent cannot tell what statuses exist or what else is returned. Adequate for the tool's low complexity, but not fully self-sufficient.

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 0%, so the description carries the parameter burden: it identifies challengeId as a lobby identifier and explains that omitting it switches the tool to list mode. That meaning is not recoverable from the bare string schema. It stops short of stating the ID's format, which the 64-char maxLength hints at but never explains.

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 a specific verb ('Status of') and resource ('challenge lobby'), and adds a second mode ('list open lobbies'), so an agent knows exactly what it retrieves. It does not explicitly contrast with siblings like open_challenge or join_challenge, which keeps it at 4 rather than 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?

It gives one concrete usage rule — omit challengeId to list open lobbies — which is genuinely actionable. However, it never says when to prefer this over the obvious alternatives (join_challenge, open_challenge, get_heat_result), so the routing guidance is implied rather than explicit.

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