Skip to main content
Glama

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.8/5.0
Behavior5/5

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

Adds substantial information beyond the annotations: it fans out to independent providers, computes a consensus winner/score, returns an ML-DSA-65 signed receipt anchored on Base, and costs $0.50 USDC per call. Pricing and the payment/auth implication are exactly the kind of operational detail annotations cannot carry, and nothing contradicts readOnlyHint=true.

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?

Front-loaded and dense: purpose, mechanism, use case, coverage, price, each in a single sentence. The price is redundantly stated twice ('$0.50. $0.50 USDC per call.'), which is the only real waste.

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?

For a paid, open-world read with no output schema, the description should say more about the returned artifact (which fields carry score/winner, what a disagreement or unavailable game yields). It covers the receipt concept but leaves the return shape and failure modes undefined, and four required parameters go unexplained.

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% across 5 parameters, so the description must compensate and largely does not. The sport list ('Supports NFL, NBA, MLB, NHL, Soccer, Esports') loosely maps to the sport enum, but home_team/away_team naming conventions, the game_date format, and the optional 'competition' field are never explained.

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 specific verb and resource ('sports game outcome verification') plus the mechanism (multi-provider consensus, signed receipt). An agent can tell what it produces. However, it never contrasts itself with the closely named sibling get_resolve_game_outcome, leaving that distinction to inference.

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?

Gives a concrete triggering scenario: 'Use when a prediction market or betting agent needs trustless proof of a game result for dispute resolution.' That is a clear when-to-use signal. It stops short of naming an alternative tool or stating when not to use it (e.g. live/in-progress games).

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