Skip to main content
Glama

get_resolve_game_outcome

Read-only

Binary prediction market resolver for sports outcomes. Evaluates home_win, away_win, draw, or not_draw conditions via multi-source consensus. Returns boolean resolution with ML-DSA-65 signed receipt verifiable on Base, designed for autonomous on-chain settlement. Supports NFL, NBA, MLB, NHL, Soccer, Esports. $0.50. $0.50 USDC per call.

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": {
      "sport": "<sport>",
      "home_team": "<home_team>",
      "away_team": "<away_team>",
      "game_date": "<game_date>",
      "resolve_for": "<resolve_for>"
    },
    "name": "get_resolve_game_outcome"
  }
}

Input Schema

NameRequiredDescriptionDefault
sportYes
away_teamYes
game_dateYes
home_teamYes
competitionNo
resolve_forYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint, destructiveHint=false), and the description adds genuinely new behavior: multi-source consensus evaluation, a boolean result, an ML-DSA-65 signed receipt verifiable on Base, and a per-call price of $0.50 USDC. What it omits is what happens on conflicting sources or unresolved games, and whether the call is idempotent or billable on failure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The first sentence front-loads purpose well and the receipt/settlement details are useful, but the price is duplicated verbatim ('$0.50. $0.50 USDC per call.'), which is pure waste. Most remaining sentences do earn their 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?

With no output schema, the description does the right thing by describing the return value (boolean plus signed receipt on Base). However, for a paid, six-parameter resolution tool it leaves the input contract under-specified and says nothing about ambiguous or postponed games, consensus failure, or latency.

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?

Schema description coverage is 0%, so the description must carry all six parameters, but it only loosely gestures at two: the sport list ('NFL, NBA, MLB, NHL, Soccer, Esports') and the resolve_for conditions. It never explains team-name format, the YYYY-MM-DD date pattern, the optional competition field, and its sport list is inaccurate — the enum includes tennis_atp (unmentioned) and splits esports into specific leagues.

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?

States a concrete verb and resource — 'Binary prediction market resolver for sports outcomes' — and enumerates the resolution conditions (home_win, away_win, draw, not_draw). It does not explicitly distinguish itself from the sibling get_verify_game_outcome, so an agent must infer that this one resolves while the sibling verifies.

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 through 'designed for autonomous on-chain settlement', which hints at the settlement context but never states when to prefer this over get_verify_game_outcome or what preconditions must hold. No exclusions or alternative routing are given.

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