Skip to main content
Glama

Stratalize Intelligence

Get Resolve Game Outcome

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

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), and the description adds substantive behavior on top: multi-source consensus resolution, an ML-DSA-65 signed receipt verifiable on Base, supported sports, and a per-call price. It stops short of describing failure/ambiguity handling (postponed games, disputed results) or latency, which is the remaining gap.

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 content is dense and front-loaded with the core purpose, but the cost is stated twice ('$0.50. $0.50 USDC per call.'), which is redundant filler. The remaining sentences each add information, so only the duplicated pricing line wastes space.

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?

There is no output schema, and the description does cover the return ('boolean resolution with ML-DSA-65 signed receipt'). For a 6-parameter, paid, on-chain-settlement tool with 0% schema coverage, it should still say what happens on unresolvable or ambiguous games, how team names are matched, and what the optional competition parameter does.

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 description coverage is 0%, so the description must carry parameter meaning; it does explain resolve_for's four conditions and loosely enumerates sports, but the listed leagues (NFL, NBA, MLB, NHL, Soccer, Esports) do not match the schema enums (which include tennis_atp and omit nothing else), and home_team, away_team, game_date, and especially the optional competition field get no semantics at all.

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 opens with a specific verb+resource ('Binary prediction market resolver for sports outcomes') and enumerates the four resolvable conditions, so an agent knows exactly what computation happens. It never names the closest sibling (get_verify_game_outcome), so the boundary between resolving and verifying is left for the agent to infer.

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 contextual usage ('designed for autonomous on-chain settlement') and lists supported leagues, which implies when the tool applies. However, there is no explicit when-to-use/when-not-to-use statement and no routing to get_verify_game_outcome for the post-resolution check, so usage is only implied.

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