Context7: External Library Documentation
Use Context7 to look up current library APIs instead of guessing from training data.
When to Use
- Implementing with external libraries - Check current API before writing code
- Debugging library errors - Verify correct usage patterns
- User asks "how do I use X" - Get up-to-date examples
- Uncertain about library API - Don't guess, look it up
- Library version matters - Context7 has version-specific docs
Workflow
resolve-library-id(libraryName="tokio", query="async runtime spawn tasks")
query-docs(libraryId="/tokio-rs/tokio", query="how to spawn async tasks")
Always call resolve-library-id first to get the correct library ID, then query-docs with a specific question.
When NOT to Use
- Standard library features (Rust std, Python builtins, etc.)
- Confident in the API from recent experience
- Simple operations with well-known patterns
Example
User asks about async file reading with tokio:
resolve-library-id(libraryName="tokio", query="async file reading")
query-docs(libraryId="/tokio-rs/tokio", query="async file reading tokio::fs")
- Use the returned docs to write correct code