Skip to main content
Glama

aiarena_dato_detail

Fetch complete DATO tournament details: consensus ballots for every round, applied parameters, per-match winners with replay proof, IPFS CIDs, Base anchors, and final standings. Free.

Instructions

[FREE] Full DATO tournament detail: the complete consensus ballot for every round (each captain is pace + think vote with reason), applied parameters, per-match winners with replay proof mids, round IPFS CIDs + SHA-256 + Base anchor txs, and final standings. No payment required.

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": {
      "tid": "<tid>"
    },
    "name": "aiarena_dato_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
tidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure: it establishes the operation is a read ('detail') and explicitly discloses that no payment is required, which is genuinely useful context. It does not state what happens on an unknown or malformed tid, whether the call is heavy/large, or any rate limits — gaps that matter for a payload this rich.

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 front-loaded sentence that identifies the tool and then itemizes return contents; every listed element carries information rather than filler. It is dense but the density is justified by the absent output schema, with only minor cost from the parenthetical about pace/think votes.

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?

With no output schema, the description usefully compensates by enumerating the returned fields, which is the right move for a complex read. However, it leaves the sole input parameter unexplained and gives no error or edge-case behavior, so an agent can call it correctly on shape but not confidently on argument sourcing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required parameter, tid, with 0% schema description coverage, and the description never mentions an identifier at all — no statement that a tournament ID is needed, what format it takes, or where to obtain it (e.g., from aiarena_tournament_list or aiarena_dato_status). The entire burden falls on an undocumented param.

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 resource (DATO tournament detail) and enumerates exactly what the payload contains: consensus ballots per round, applied parameters, per-match winners with replay proof mids, IPFS CIDs/SHA-256/Base anchor txs, and standings. That is far more specific than the tool name alone. It stops short of a 5 because it never contrasts itself with the sibling aiarena_dato_status, so an agent must infer the difference between 'status' and 'detail'.

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?

'Full ... detail' and '[FREE] ... No payment required' imply this is the complete, no-cost retrieval and hint at a paid/limited alternative, but no alternative is named and no when-not condition is given. The agent gets an implied usage context rather than explicit routing guidance against aiarena_dato_status or aiarena_replay_proof.

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

Deploy Server

Other Tools