Tool selection guide
When TypeScript semantic tools help
TGlider provides semantic workspace intelligence for TypeScript and JavaScript through MCP.
Use it when project ownership, exports, symbol identity, diagnostics, or code relationships matter across a JS or TS workspace.
Choose TGlider from the question
Orient in a workspace
Identify projects, packages, configuration, and ownership before editing.
get_workspace_rootlist_workspace_projectsget_projectsget_project_info- Workspace tools report the loaded project contexts.
- Package and module context can distinguish similar files in different projects.
Resolve symbols and exports
Find declarations, references, implementations, and public API surfaces.
find_codesemantic_queryfind_referencesfind_implementationslist_exportslist_project_apis- Symbol results carry reusable keys and source spans.
- Export tools distinguish a project API from a local name match.
Inspect diagnostics and calls
Read diagnostics, callers, outgoing calls, and bounded impact.
get_diagnosticsdiagnostic_hotspotsfind_callersget_outgoing_callsanalyze_change_impact- Diagnostic results can be filtered and grouped.
- Call and impact tools start from semantic symbol identity.
Map dependencies
Inspect project and file relationships before an architecture change.
get_project_dependenciesget_file_dependentsfind_dependency_pathdetect_cycles- Dependency tools return project and file ownership with graph edges.
- Module-resolution evidence explains how a specific import resolves.
Analyze live documents
Keep semantic reads aligned with unsaved document text.
open_documentupdate_documentapply_document_editsclose_document- Open documents have explicit versions.
- Diagnostics and navigation can use the in-memory document state.
Preview a rename or edit
Compute changes before writing them to the workspace.
compute_rename_editsrename_symbolwrite_fileorganize_imports- Preview rename edits before applying them.
- Use diagnostics after a change to inspect the same workspace scope.
Use another tool when
- Use Scout for literal and regex text hunts. TGlider does not expose a text-search tool.
- Use Scout for fuzzy, semantic, hybrid, or structural retrieval across non-JS and non-TS files.
- Use package scripts and the TypeScript compiler for build and test execution.
- TGlider needs a loaded workspace. This page makes no latency, token, or accuracy comparison with CLI or LSP tools.
About comparisons
This page records capability differences and tool boundaries only.
Future benchmark claims must publish the repositories, tasks, client setup, models, commands, and raw results.