Update to FCData

{
  "description": "Check FC Ultimate Team card price observations and 24-hour or seven-day price history with FCData, including console/PC differences, missing prices and observation freshness. Use for card market questions, not purchases, forecasts, or unrelated financial questions.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 222
    }
  ],
  "name": "check-card-prices",
  "skill_md_contents": "---\nname: check-card-prices\ndescription: Check FC Ultimate Team card price observations and 24-hour or seven-day price history with FCData, including console/PC differences, missing prices and observation freshness. Use for card market questions, not purchases, forecasts, or unrelated financial questions.\n---\n\nUse the `fcdata` MCP server's `get_card_prices` and `get_price_history` tools.\nUse `search_cards` or `get_card` when a confirmed card variant is still needed.\n\n1. Resolve edition and variant first. Default to FC27 (`gameYear: 2027`);\n   label FC26 (`2026`) as historical. Use only confirmed `definitionId` values.\n   Clarify multiple matching variants instead of guessing one by player name.\n2. Confirm console versus PC when unknown; retain that choice for follow-ups.\n   “And on PC?” changes the platform and requires a new price query.\n3. Retrieve up to five variants per price call. Report coins, platform and\n   original `observedAt`. These are stored market observations, not executable\n   offers. Calling the tool again does not make an old observation current.\n4. Translate `availability` and `freshness` into clear language. Unavailable\n   prices are unknown, not zero; never substitute a console price for PC.\n   A future or missing timestamp has unknown freshness. A recent timestamp\n   is within the server's 15-minute display threshold, not a delivery guarantee.\n5. For history choose only `24h` or `7d`, matching the user's question. Use\n   `get_price_history` to display its centered interactive chart with card\n   artwork and console/PC and period controls. Do not replace that chart with\n   `render_cards`. Controls retain the confirmed edition and variant.\n   Use returned time bounds and the selected platform's summary. Preserve null\n   points as observation gaps. `pointsSampled` means the server reduced the\n   points; its summary still uses the complete source series. When\n   `hasObservationGaps` is true, do not connect sampled points into a continuous\n   chart: sampling may omit individual null markers. If `hasSufficientData` is false, explain that a\n   reliable trend is unavailable. Historical movement is not a forecast.\n6. Link the card name to its returned `url`, and provide the FCData card link\n   for interactive inspection. Answer the user's price question in ChatGPT.\n7. Handle explicit errors separately from absent quotes. For a retryable\n   failure offer a retry or the confirmed card link; never fabricate prices.\n\nUse the user's language. Do not invoke tools for unrelated finance questions,\nrequest EA account credentials, create alerts, initiate purchases or claim\nan exact future price. Account actions and MCP Events are later phases.\n\nExamples:\n\n- “What do these three cards cost on PC?”: query those canonical IDs on PC;\n  show each observed price and time, retaining unavailable entries.\n- “How did this console card change over seven days?”: query `7d` on console;\n  show the returned change and data sufficiency, with the FCData card link.\n- “Buy this player for me”: explain that purchases are not supported.\n"
}