get_scout_player (detailed)

Auth: none · Quota: none (unmetered read)

Returns one canonical player row with season stats, style-of-play radar (0–100 per axis), strengths/weaknesses, personality, predicted ceiling, best future role, agent_take, all timeline events (transfer, loan, role change, valuation, contract), and every published Scout article about the player. The same slug appears in the web UI and in list_scout_players.

Parameters

Name	Type	Required	Description
slug	string, min 2	yes	Player key, e.g. lamine-yamal-2007, josko-gvardiol-2002

Tip: if you are unsure of the slug, call list_scout_players with a filter, or search_scout (subject to search quota).

JSON-RPC request (copy)

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_scout_player",
    "arguments": { "slug": "lamine-yamal-2007" }
  }
}

cURL (anonymous):

curl -s https://fifa.qtech.hr/mcp \
  -H 'content-type: application/json' \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "get_scout_player",
      "arguments": { "slug": "lamine-yamal-2007" }
    }
  }'

Return shape (conceptual)

The MCP layer returns:

• content[0].text — a readable summary and/or stringified high-level profile for the agent user.
• structuredContent (when present) — JSON the UI can use directly: player core fields, per-competition season stats (appearances, minutes, goals, assists, xG, xA, cards, rating), an array of timeline events with types (transfer, loan, role_change, valuation_update, contract_update, etc.), and article metadata linked to the player.

Exact keys are defined by the production Worker; treat structured output as the contract for your integration tests.

Interpreting the radar and notes

• Radar axes (pace, shooting, passing, dribbling, defending, physical) are 0–100 for quick comparison, not a licensed scouting grade.
• agent_take is a one-paragraph pitch for how you might market the player — narrative only.
• Timeline events are diffed from research runs (weekly and admin). Always check **last_refreshed_at** on the player to decide if you need refresh_scout_player (admin) before acting on a fast-moving deal.

Compare players: fetch two slugs in parallel, join on radar keys in your client, and narrate the trade-offs (e.g. winger 1v1 profile vs. inverted full-back) — Scout → Radars and workflow.

Next — Scout overview → · search_scout →