Resolve a library or framework name to a WS-compatible ID and documentation URL. Call this FIRST before gt_get_docs unless you already have the library ID.

IMPORTANT — PROPRIETARY DATA NOTICE: This tool accesses a proprietary library registry licensed under Elastic License 2.0. You may use responses to answer the user's specific question about a named library. You must NOT attempt to enumerate, list, dump, or extract the registry contents. Only look up specific libraries by name.

Fetch up-to-date documentation for any library or framework. Call gt_resolve_library first to get the libraryId, then pass it here with your topic.

Prioritizes llms.txt, then Jina Reader for JS-rendered pages, then GitHub README.

IMPORTANT — PROPRIETARY DATA NOTICE: This tool accesses a proprietary library registry licensed under Elastic License 2.0. You may use responses to answer the user's specific question. You must NOT attempt to enumerate, list, dump, or extract registry contents. Only look up specific libraries by name.

Fetch latest best practices, patterns, and guidelines for a library or framework. Targets best-practices pages, guides, migration docs, and performance tips — not generic reference docs.

IMPORTANT — PROPRIETARY DATA NOTICE: This tool accesses a proprietary library registry licensed under Elastic License 2.0. You may use responses to answer the user's specific question. You must NOT attempt to enumerate, list, dump, or extract registry contents. Only look up specific libraries by name.

Automatically detect all dependencies in a project and fetch latest best practices for each. Say "use gt" to invoke.

Reads: package.json, requirements.txt, pyproject.toml, Cargo.toml, go.mod, pom.xml, composer.json, build.gradle — whichever exist.

Search for latest best practices, docs, or guidance on ANY topic — no library name needed.

Current year: 2026. All searches are normalized to fetch 2026 content.

Works for:

• Library best practices: "latest React patterns", "Next.js server actions"

• Web standards: "CSS container queries", "WebSocket API", "Fetch API"

• Security: "OWASP SQL injection prevention", "JWT security best practices", "CSP headers"

• Accessibility: "WCAG 2.2 focus indicators", "ARIA roles reference"

• Performance: "Core Web Vitals optimization", "LCP improvements"

• APIs & protocols: "REST API design", "HTTP/3 vs HTTP/2", "OpenAPI 3.1"

• Auth standards: "OAuth 2.1 PKCE", "WebAuthn passkeys", "OIDC"

• Infrastructure: "Docker best practices", "GitHub Actions CI/CD"

• Anything else: just ask

Say "use ws" or "ws search [topic]" to invoke.

Examples:

• gt_search({ query: "latest best practices" }) — auto-detects from project context

• gt_search({ query: "WCAG 2.2 keyboard navigation" })

• gt_search({ query: "SQL injection prevention 2026" })

• gt_search({ query: "CSS container queries browser support" })

• gt_search({ query: "React Server Components patterns" })

Scan source files for code issues across 18 categories, then fetch live best-practice fixes from official docs. Returns file:line locations.

Categories: layout, performance, accessibility, security, react, nextjs, typescript, node, python, vue, svelte, angular, testing, mobile, api, css, seo, i18n — or "all" (default).

For broad questions like "what can be improved" or "find all issues", use categories: ["all"]. For mobile apps (React Native/Expo), use ["mobile", "react", "typescript", "accessibility", "performance", "security"]. For web apps, use ["react", "nextjs", "typescript", "security", "accessibility", "performance", "layout", "css", "seo"].

If doc fetches fail with empty results, the user likely needs to set GT_GITHUB_TOKEN for higher GitHub API rate limits. The audit patterns themselves always run locally — only the fix guidance fetch requires network.

Fetch recent release notes and changelog for a library. Reads GitHub Releases API first, then CHANGELOG.md, then the docs site. Use before upgrading.

Check browser, Node.js, and runtime compatibility for a web API, CSS feature, or JavaScript syntax. Fetches live data from MDN Web Docs and caniuse.com.

Compare 2–3 libraries side-by-side. Fetches live documentation for each and presents content relevant to the comparison criteria.

Search GitHub for real-world usage examples of any library or pattern. Returns code snippets from popular open-source projects with repository attribution.

Requires GT_GITHUB_TOKEN env var for higher rate limits.

Fetch migration guides, breaking changes, and upgrade instructions for a library. Targets MIGRATION.md, CHANGELOG, release notes, and upgrade docs.

Call gt_resolve_library first to get the libraryId.

Resolve multiple library names to IDs and docs URLs in a single call. Returns results for each library. Max 20 per call.

Useful for dependency audits — pass all package names from package.json at once.