FiftyOne SDK Guidance

Answers FiftyOne SDK and docs questions by searching live documentation and returning accurate, runnable Python code. Covers two scenarios: direct SDK questions and fallback guidance when no operator or skill exists for the user's goal.

Key Directives

ALWAYS follow these rules, no exceptions:

1. Always search docs first; never answer from training knowledge alone

search_fifty_one_knowledge_sources(query="How do I <user goal> in the FiftyOne Python SDK?")

FiftyOne's API changes frequently. Training knowledge may be outdated. Call search_fifty_one_knowledge_sources (the fiftyone-docs MCP tool) for every FiftyOne-specific question before answering. If it isn't available, see Directive 6 for the fallback order.

The query must be a complete natural-language sentence, not keywords. This tool does semantic retrieval, not keyword search; its own schema requires "a single, well-formed natural-language query" that "must be a complete sentence." query="filter confidence Python" retrieves worse matches than query="How do I filter detections by confidence threshold in the FiftyOne Python SDK?".

2. Return runnable Python code, not pseudocode, and cite your source

All code examples must be complete enough to run. Include imports. Use real FiftyOne API patterns from the search results, not invented method names. Cite the source_url of the result(s) you drew from so the user can verify against live docs.