Skip to main content
Glama

Stratalize Intelligence

Get Verify Game Outcome

get_verify_game_outcome
Read-only

Multi-source sports game outcome verification with cryptographic receipt. Queries independent data providers, reaches consensus on final score and winner, returns ML-DSA-65 signed receipt anchored on Base. Use when a prediction market or betting agent needs trustless proof of a game result for dispute resolution. 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>"
    },
    "name": "get_verify_game_outcome"
  }
}

Input Schema

NameRequiredDescriptionDefault
sportYes
away_teamYes
game_dateYes
home_teamYes
competitionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, and the description adds real context beyond them: multi-provider querying, consensus logic, an ML-DSA-65 signature anchored on Base, and a per-call price of $0.50 USDC. It does not say what happens when providers disagree or a game is not found, which is the main behavioral gap for a consensus tool.

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?

The capability and the trust framing are front-loaded and each sentence conveys something useful. The only waste is the redundant cost statement ('$0.50. $0.50 USDC per call.'), which repeats the same fact twice in two formats.

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, so the description bears responsibility for explaining the return value; it names the consensus result and the signed receipt but not the receipt's fields or verification path. Combined with the undocumented 'competition' parameter and ambiguous team-name convention, a caller would still have to guess at invocation details.

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 parameter meaning, and it only partially does. It lists supported leagues, but 'competition' is never explained, team-name format (full name vs. abbreviation) and timezone for game_date are undefined, and the league list omits tennis_atp, ncaaf/ncaab details that appear in the enum, so the description actually understates the supported values.

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 uses a specific verb and resource ('queries independent data providers, reaches consensus on final score and winner, returns ML-DSA-65 signed receipt'), which is far more informative than the title 'Get Verify Game Outcome'. It does not name or distinguish itself from the sibling get_resolve_game_outcome, so an agent cannot tell from the text alone which of the two to pick.

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?

It gives a concrete use case and audience ('Use when a prediction market or betting agent needs trustless proof of a game result for dispute resolution'), which is enough to route a caller. It stops short of explicit exclusions or of pointing to the resolution/verification alternatives, so the when-not guidance is missing.

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