Resolve Entities

​

What this tool is best at

​

Choose this tool when

• the host does not yet know which sport, competition, competition season, series, participant, or venue the user means.
• Source ownership: GSD Lookup primary

​

Use something smaller or different when

• the caller already has a stable provider ref and only needs schedule, standings, watchability, or event detail.

​

Inputs you need

​

Plain-English prerequisites

• This tool does not require a prerequisite ID beyond the scoped inputs shown below.

​

Required inputs in the public contract

​

Optional inputs in the public contract

​

Notes on optional inputs

• Use entityType when the host already knows the kind of thing the user means and wants tighter candidate ranking.
• Use resolutionIntent when one lexical family maps to multiple sibling series and the host already knows the next view it wants, such as rankings.
• Use limit to keep candidate sets compact for low-token flows.
• Use resolutionProfile to trade off latency against exhaustive live traversal. complete is supported for non-participant entity types only and may be materially slower because it exhausts the live frontier instead of stopping early.
• crosswalkConfidence is scored per candidate on a 0.00-1.00 scale. Treat 0.90-1.00 as high confidence, 0.60-0.89 as mixed confidence that should not silently deepen across providers, 0.01-0.59 as low confidence, and null as no crosswalk.

​

Sequencing guidance

• Pick one candidate and preserve its provider refs before calling a deeper tool.
• Use crosswalkConfidence to decide whether hybrid enrichment is safe or whether the host should ask a narrowing question.

​

Response highlights

• Bounded candidate rows with entityType, displayName, participantType for participant rows, gsdRefs, onRefs, and programHints.
• Crosswalk confidence that tells the host whether it can safely enrich across providers or should ask a narrowing question first.
• Machine-readable data.traversal metadata that tells the host which live frontier was explored, whether it was complete, and where coverage stayed partial.
• Candidate ordering is deterministic: intent fit first, then lexical score, then lexical tie-breaks, then entity-type ordering, then stable ID.

​

Response shape

​

Reuse next

• gsdRefs for GSD-first tools such as list_schedule, get_competition_hub, get_event_summary, and get_standings.
• onRefs for program-context and watchability flows such as get_program_context, get_watch_availability, and list_programs_for_entity.

​

Example requests

{
  "jsonrpc": "2.0",
  "id": "tool-call-1",
  "method": "tools/call",
  "params": {
    "name": "resolve_entities",
    "arguments": {
      "query": "Premier League",
      "entityType": "competition",
      "resolutionProfile": "balanced",
      "resolutionIntent": "generic",
      "limit": 5
    }
  }
}

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": "resolve_entities",
    "arguments": {
      "query": "Premier League",
      "entityType": "competition",
      "resolutionProfile": "balanced",
      "resolutionIntent": "generic",
      "limit": 5
    }
  }
}'

const payload = {
    "jsonrpc": "2.0",
    "id": "tool-call-1",
    "method": "tools/call",
    "params": {
      "name": "resolve_entities",
      "arguments": {
        "query": "Premier League",
        "entityType": "competition",
        "resolutionProfile": "balanced",
        "resolutionIntent": "generic",
        "limit": 5
      }
    }
  };

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": "resolve_entities",
    "arguments": {
      "query": "Premier League",
      "entityType": "competition",
      "resolutionProfile": "balanced",
      "resolutionIntent": "generic",
      "limit": 5
    }
  }
}

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))

​

Related tools

​

Previous-step tools

• No common previous-step tools beyond already knowing the right IDs or scope.

​

Next-step tools

• list_schedule
• get_competition_hub
• list_watchable_schedule
• get_program_context

​

Alternative tools

• No common alternatives.

​

Prompt patterns this tool fits

• “Resolve this league/team/event first.”
• “I don’t know which IDs I need yet.”

​

Common mistakes

• Treating provider refs like server-generated canonical IDs. The caller must preserve whether a ref came from GSD or On.
• Using it as a replacement for a direct profile or schedule call after the IDs are already known.