Unblocked

Retrieve repository coding rules and conventions. Returns all rules for a repository, or a specific rule by ID. Rules are extracted from CLAUDE.md, AGENTS.md, .cursorrules, CONTRIBUTING.md, and other convention files in the repository.

Retrieve and hydrate content from supported URLs. Provide one URL per line. Supports the following URL patterns: - GitHub on github.com: PRs, issues, and file blobs such as https://github.com/<owner>/<repo>/pull/<number>, https://github.com/<owner>/<repo>/issues/<number>, and https://github.com/<owner>/<repo>/blob/<ref>/<path>. - Google Drive for Workspaces on docs.google.com: documents such as https://docs.google.com/document/d/<fileId>, https://docs.google.com/spreadsheets/d/<fileId>, https://docs.google.com/presentation/d/<fileId>, and https://docs.google.com/file/d/<fileId>. - Google Drive for Workspaces on drive.google.com: documents such as https://drive.google.com/document/d/<fileId>, https://drive.google.com/spreadsheets/d/<fileId>, https://drive.google.com/presentation/d/<fileId>, and https://drive.google.com/file/d/<fileId>. - Unblocked on docs.getunblocked.com: documents such as https://docs.getunblocked.com/<path>. - Unblocked on getunblocked.com: threads such as https://getunblocked.com/dashboard/team/<teamId>/thread/<threadId>.

Retrieve institutional context that code search cannot provide — WHY, WHO, WHEN behind the code. Primary Unblocked research tool; reach for it first for synthesis across sources. One call searches every indexed source: documentation, PRs, messaging (Slack/Teams), issues (Jira/Linear/GitHub), customer support tickets (Zendesk), code (semantic search + file reads), code history, incidents, public web, internal URLs. Composes semantic search, code search, file reads, PR/issue queries, messaging search, and incident lookups. ## When to call Call proactively at the start of any non-trivial task, and whenever you hit an unknown. Do not wait for the user to ask. - Planning, investigation, refactor, migration, or feature work. Fire in the same tool block as your first Explore/Grep/Read calls — complementary, zero latency cost. - "Why does this exist" or "why is it done this way" questions. Code reading cannot answer these. - Behavior doesn't match the code. Check history before assuming the code is wrong. - Unfamiliar class, service, endpoint, flag, config key, or error string while reading or editing. - Before writing new code. Check whether the pattern, bug, fix, helper, or abstraction already exists. - Incident, alert, or outage. Connect affected systems to recent changes and prior fix patterns. - Filtered activity lookups. "PRs merged last week in auth service", "open incidents tagged ingestion", "Jira epics in PROJ from Q1". - Ambiguous user requests. Find the team's prior framing before guessing. - Before recommending a solution. Verify the approach hasn't been tried, rejected, or superseded. ## When NOT to call - Known URL in hand. Use `context_get_urls` — faster, deterministic, returns full hydrated content. Fall back here only if the URL pattern is unsupported. If unsure, call. Missed context is expensive; recall misses are cheap.