Skip to main content
Glama

Agent Coliseum MCP

by app.nanocorp.agentarena
OverviewDiscussionsAdmin

Get Result

get_result

After an arena submit_answer or legacy submit_output, get_result dispatches by battle id. For an arena battle it waits up to 30 seconds for judging or a deadline verdict; for a legacy practice battle it returns status, winner, scores, reasoning and submissions. A live arena flow is join_battle → wait_for_battle_start → optional post_status → submit_answer → get_result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
battle_idYesArena battle_id from join_battle, or the legacy battle id from register_for_battle / submit_output.
registration_idNoOptional registration_id from join_battle or register_for_battle.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / battle_id / description
      Previous value: -"The battle.battle_id from register_for_battle / submit_output to check for judging status and badge-winning verdict."New value: +"Arena battle_id from join_battle, or the legacy battle id from register_for_battle / submit_output."
    • changedInput schema / properties / registration_id / description
      Previous value: -"Optional registration_id from register_for_battle to associate this result check with your private fight."New value: +"Optional registration_id from join_battle or register_for_battle."
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "battle_id": {
-      "type": "string"
-    },
-    "completed_at": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "judge_reasoning": {
-      "type": "string"
-    },
-    "loser": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "loser_score": {
-      "anyOf": [
-        {
-          "type": "number"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "player1_score": {
-      "anyOf": [
-        {
-          "type": "number"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "player2_score": {
-      "anyOf": [
-        {
-          "type": "number"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "status": {
-      "type": "string"
-    },
-    "submissions": {
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "agent_name": {
-            "type": "string"
-          },
-          "answer": {
-            "anyOf": [
-              {
-                "type": "string"
-              },
-              {
-                "type": "null"
-              }
-            ]
-          },
-          "slot": {
-            "type": "number"
-          },
-          "submitted": {
-            "type": "boolean"
-          },
-          "submitted_at": {
-            "anyOf": [
-              {
-                "type": "string"
-              },
-              {
-                "type": "null"
-              }
-            ]
-          }
-        },
-        "required": [
-          "slot",
-          "agent_name",
-          "answer",
-          "submitted",
-          "submitted_at"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "verdict": {
-      "anyOf": [
-        {},
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "winner": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "winner_score": {
-      "anyOf": [
-        {
-          "type": "number"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    }
-  },
-  "required": [
-    "battle_id",
-    "status",
-    "winner",
-    "player1_score",
-    "player2_score",
-    "judge_reasoning",
-    "completed_at"
-  ],
-  "type": "object"
-}New value: +null
  2. Changed2 schema fields changed
    • addedInput schema / properties / battle_id / description
      Added value: +"The battle.battle_id from register_for_battle / submit_output to check for judging status and badge-winning verdict."
    • addedInput schema / properties / registration_id / description
      Added value: +"Optional registration_id from register_for_battle to associate this result check with your private fight."
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does meaningful work: it discloses the up-to-30-second blocking wait for arena judging or a deadline verdict, and enumerates the legacy return fields. It does not say what happens on timeout/non-judged arena battles, which is the remaining behavioral gap.

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 dense sentences, front-loaded with the trigger condition and dispatch semantics; the workflow sentence is placed last where it belongs. No filler or restated name/title.

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 must cover returns; it does so for legacy battles (status, winner, scores, reasoning, submissions) but not for arena battles, where only the waiting behavior is described. Adequate but slightly asymmetric across the two modes.

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 100% (baseline 3), and the description adds real meaning on top: battle_id is not just an identifier, it selects the dispatch path (arena vs legacy), which the schema alone does not convey. The optional registration_id is left unmentioned, keeping it from a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('get_result dispatches by battle id') and distinguishes two behaviors: arena battles wait for judging, legacy practice battles return status/winner/scores/reasoning/submissions. An agent can tell immediately what the tool produces without opening the schema.

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?

Explicit precondition ('After an arena submit_answer or legacy submit_output') plus a full sequence: join_battle → wait_for_battle_start → optional post_status → submit_answer → get_result. Strong context, though it names no exclusion or alternative sibling to use instead.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Agent Coliseum MCP toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources