detect_sdk
ClaudeA readiness report for one game project: the engine it uses (unity, defold, js), whether the Yes2SDK is installed, the installed version, and any install steps still required. Answers "can this project compile Yes2SDK code yet?", and pairs with get_install_instructions when the SDK is missing. Two input modes, exactly one per request: - projectPath: absolute path to the project root, available when this server runs LOCALLY over stdio and can read the disk. - files: inline map of repo-relative path → contents, keyed on "game.project", "Packages/manifest.json" or "package.json" — the mode for the HOSTED/sandboxed server, which has no disk access. Project files are inspected, never modified.
get_api_reference
ClaudeThe full API reference for one Yes2SDK module — exact method signatures, parameters, return values, and per-platform behavior. Modules: overview, lifecycle, ads, analytics, auth, banners, data, errors, friends, game, player, score, session, leaderboard, stats, iap, config, review, upcoming.
get_compliance_rule
ClaudeOne Yes2SDK platform-compliance rule by id (e.g. 'P-002', 'U-001', 'CG-003'): its severity (FAIL/WARN/INFO), the platform it applies to, what it checks, and the concrete fix(es). Answers "what is this rule id and how do I satisfy it?" when validate_integration or get_platform_requirements surfaces one. A platform's full rule set comes from get_platform_requirements(platform); grading a build is validate_integration.
get_install_instructions
ClaudeVersion-pinned steps for adding the Yes2SDK to a Unity, Defold, or JavaScript game, including post-install setup such as Unity's required WebGL template, and a check that confirms the SDK resolves. Answers "how do I add the Yes2SDK to this project?" — until these steps complete, code referencing the Yes2SDK namespace (Unity), the yes2sdk module (Defold), or window.Yes2SDK (JS) will not compile. Returns text; the project is never modified, and what is already installed is reported by detect_sdk instead.
get_platform_capabilities
ClaudeWhich Yes2SDK modules are supported on which platforms (poki, crazygames, yandex, gamedistribution, youtube), as a Ready / Partial / not-offered matrix, optionally narrowed to one platform (a column) or one module (a row). Answers "do I need to guard this module behind isSupported()?" — Friends and Auth are CrazyGames/Yandex-only, banners are not offered on Poki. Reads the bundled API docs; per-method detail comes from get_api_reference(module).
get_platform_requirements
ClaudeThe compliance rules a build must satisfy for one platform (poki, crazygames, yandex, gamedistribution, youtube), each as 'id [severity]: description' — the same checks validate_integration runs. Answers "what do I have to get right for this platform?" up front; one rule's detail and fix comes from get_compliance_rule(ruleId), and an actual build is graded by validate_integration. Returns the rule list only; no build is evaluated.
get_quickstart
ClaudeThe full quickstart integration guide for one target platform (poki, crazygames, yandex, gamedistribution, youtube): mandatory call sequence, per-engine examples, critical rules, and the common rejection reasons. The starting point for a new integration, before the first SDK call is written.
list_sdk_modules
ClaudeThe names of every Yes2SDK API reference module. A directory for get_api_reference(module) and the yes2sdk://docs/{module} resource when the right module name is not known yet.
search_docs
ClaudeKeyword search across the Yes2SDK documentation — quickstarts, API reference, dashboard guide, integration rules — returning up to the top 5 matching sections with the doc slug of each, for follow-up via get_quickstart(platform) or get_api_reference(module). The way in when the question about integration, platform requirements, or the SDK's API is still open-ended: a specific error resolves faster through troubleshoot(symptom), and per-platform module support through get_platform_capabilities(). Searches the bundled docs only, with no web access.
troubleshoot
ClaudeThe likely cause and ordered fix for a reported Yes2SDK integration symptom, given an error string or a plain-language description. Covers the common failures: missing namespace or module (SDK not installed), window.Yes2SDK undefined, Unity build-guard and template problems, Defold editor no-ops, rewards not granted, and platform rejections such as ads without gameplayStop or an unbundled SDK. Each answer points at the tool that resolves it (detect_sdk, get_install_instructions, get_compliance_rule, validate_integration), or at where to look next when nothing matches.
validate_integration
ClaudeA pre-upload verdict on a Yes2SDK game, checked against the real platform rejection rules and reported as FAIL/WARN/INFO findings. Answers "would this build be rejected?" for a target platform, using either or both of the two modes below. 1) STATIC build checks — two ways to supply the build: a) buildPath: absolute path to an ALREADY-EXTRACTED build folder, available when this server runs LOCALLY over stdio; the HOSTED/sandboxed server has no disk access. b) INLINE content for the hosted server: indexHtml (the index.html text), fileList (file paths in the build) and/or jsContents (the build's JS file contents). Bundling is verifiable only when jsContents is present. Covered: Yes2SDK bundled into the JS, no external <script src="http..."> tags (platforms block them), index.html present (Poki also needs index.json), and a responsive full-viewport canvas heuristic. 2) BEHAVIORAL compliance checks — eventLogJson: a JSON string of an exported Yes2SDK Inspector event log (LogEntry objects with type, method, params, success). Covers the platform's runtime rules such as gameplayStop before ads, reward only on adViewed, and no ads in the first 30s. These rules need a real run in the QA Inspector; static files cannot produce them.
