Skip to main content
Unblocked MCP tools are actively evolving. Tools and their descriptions may change over time.
unblocked_context_engine answers a focused question using organizational context that code alone does not show. Given a question, it identifies the relevant code and returns the context around it: PR discussions, past decisions, team conventions, and related documentation. Code search shows you what the code does now. The context engine adds:
  • Why it was built this way — PR discussions, design decisions, and review comments that explain the reasoning behind implementation choices.
  • What was tried before — rejected approaches, prior incidents, and previous implementations that didn’t work out.
  • What the team expects — conventions from documentation, messaging threads, and review feedback.
  • What’s documented elsewhere — related issues, documentation pages, and team discussions that provide context the code alone doesn’t show.
If your question is purely about current implementation, your agent uses code search directly. When the question involves intent, history, or conventions, the context engine surfaces the organizational knowledge behind the code.

​
When your agent uses it

  • When it needs to understand what a piece of code does and why it exists that way, such as why a payment processor retries three times instead of using exponential backoff.
  • Before finalizing a non-trivial plan, to check for prior decisions or conventions, such as whether the team has an existing retry utility.
  • When it has a focused question about a specific class, service, endpoint, or feature.

​
When your agent switches to another tool

  • If the question spans multiple systems or teams, it may escalate to research_task.
  • If it needs to look up specific records by filter (author, status, date), it will use data_retrieval.