Get Event Summary

Canonical tool name: get_event_summary Family: Deep Sports Truth Tools

What this tool is best at

Return the minimum single-event sports-truth object needed to answer what the event is and what is happening in it at summary depth.

Choose this tool when

Use it as the default entry point for one known event before fetching deeper sections.
Source ownership: GSD Lookup primary, On sports-event lookup optional when the caller already has On refs

Use something smaller or different when

the host needs play-by-play, lineups, stats, odds, or watchability detail in one response.

Inputs you need

Plain-English prerequisites

eventId: Use a GSD event ref when possible.

Required inputs in the public contract

Input	What it means
`eventId`	Provider ref for one event. Prefer the GSD-facing event ref for deep-sports tools and the selected event row for hybrid follow-ons.

Optional inputs in the public contract

Input	What it means
`idSource`	Lookup-path hint for the supplied ID. `auto` uses namespace-aware routing, `gsd` treats the ID as sports-truth-facing, and `on` treats it as On-facing. It does not change source-of-truth ownership.
`language`	Optional BCP 47 language hint such as `en-US`. Use it when the host needs translated provider output.

Notes on optional inputs

idSource=auto uses namespace-aware routing. idSource=gsd treats the supplied ID as sports-truth-facing. idSource=on treats the supplied ID as an On sports-event ref.
idSource changes how the server looks up the event, not who owns the returned event truth.

Sequencing guidance

Needed ID or scope	Call this first	Then use
scope	Tool Catalog	Start from the smallest tool that can safely anchor the workflow, then deepen only if the user asks for more.

Response highlights

The summary includes event identity, competition or series context, timing, status, participant sides, score or result snapshot when available, venue, and reusable refs.
It explicitly excludes full lineups, play-by-play, stat groups, odds tables, watchability, media, and editorial.

Response shape

Field	What it means
`data.summary`	One event summary object suitable for the default event-detail step.
`data.summary.eventId / sportsEventGId`	Reusable primary and secondary event refs.
`data.summary.name / startTime / status`	Compact event identity and timing summary.
`data.summary.participants[]`	Participant-side summary for the event.
`data.summary.competition / series / venue`	Context objects the host can reuse for breadcrumbs and drill-downs.
`data.summary.score`	Best available result snapshot for the event.
`data.summary.phaseRefs[] / overallRefs[]`	Actionable refs that may be reused by later tools.

Reuse next

Reuse provider refs returned by this tool to avoid resolving the same entity again.
Read meta.agentHints.recommendedNextTools and meta.agentHints.disambiguationOptions as non-binding host hints.

Example requests

{
  "jsonrpc": "2.0",
  "id": "tool-call-1",
  "method": "tools/call",
  "params": {
    "name": "get_event_summary",
    "arguments": {
      "eventId": "MATCH_ID"
    }
  }
}

curl "https://sports-mcp-server.etonecarg.com/" \
  -X POST \
  -H "Authorization: Bearer $SPORTS_MCP_API_KEY" \
  -H "Accept: application/json, text/event-stream" \
  -H "Content-Type: application/json" \
  -H "mcp-protocol-version: 2025-03-26" \
  -d '{
  "jsonrpc": "2.0",
  "id": "tool-call-1",
  "method": "tools/call",
  "params": {
    "name": "get_event_summary",
    "arguments": {
      "eventId": "MATCH_ID"
    }
  }
}'

const payload = {
    "jsonrpc": "2.0",
    "id": "tool-call-1",
    "method": "tools/call",
    "params": {
      "name": "get_event_summary",
      "arguments": {
        "eventId": "MATCH_ID"
      }
    }
  };

const response = await fetch("https://sports-mcp-server.etonecarg.com/", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.SPORTS_MCP_API_KEY!}`,
    Accept: "application/json, text/event-stream",
    "Content-Type": "application/json",
    "mcp-protocol-version": "2025-03-26",
  },
  body: JSON.stringify(payload),
});

const data = await response.json();
console.log(JSON.stringify(data, null, 2));

import json
import os

import requests

payload = {
  "jsonrpc": "2.0",
  "id": "tool-call-1",
  "method": "tools/call",
  "params": {
    "name": "get_event_summary",
    "arguments": {
      "eventId": "MATCH_ID"
    }
  }
}

response = requests.post(
    "https://sports-mcp-server.etonecarg.com/",
    headers={
        "Authorization": f"Bearer {os.environ['SPORTS_MCP_API_KEY']}",
        "Accept": "application/json, text/event-stream",
        "Content-Type": "application/json",
        "mcp-protocol-version": "2025-03-26",
    },
    json=payload,
    timeout=30,
)

response.raise_for_status()
print(json.dumps(response.json(), indent=2))

Previous-step tools

Next-step tools

Alternative tools

No common alternatives.

Prompt patterns this tool fits

Use get_event_summary when the host already knows the right scope and needs this job directly.

Common mistakes

Calling get_event_summary before the host has the right provider refs or bounded window.
Using get_event_summary when a smaller sibling tool would answer the question more directly.

Getting Started

Concepts

Guides

Tools

Tool Reference

Reference

What this tool is best at

Choose this tool when

Use something smaller or different when

Inputs you need

Plain-English prerequisites

Required inputs in the public contract

Optional inputs in the public contract

Notes on optional inputs

Sequencing guidance

Response highlights

Response shape

Reuse next

Example requests

Previous-step tools

Next-step tools

Alternative tools

Prompt patterns this tool fits

Common mistakes

​What this tool is best at

​Choose this tool when

​Use something smaller or different when

​Inputs you need

​Plain-English prerequisites

​Required inputs in the public contract

​Optional inputs in the public contract

​Notes on optional inputs

​Sequencing guidance

​Response highlights

​Response shape

​Reuse next

​Example requests

​Related tools

​Previous-step tools

​Next-step tools

​Alternative tools

​Prompt patterns this tool fits

​Common mistakes

What this tool is best at

Choose this tool when

Use something smaller or different when

Inputs you need

Plain-English prerequisites

Required inputs in the public contract

Optional inputs in the public contract

Notes on optional inputs

Sequencing guidance

Response highlights

Response shape

Reuse next

Example requests

Related tools

Previous-step tools

Next-step tools

Alternative tools

Prompt patterns this tool fits

Common mistakes