Skip to content
Notis

Check package ambiguity before you query Context7

Resolve the package identity first so every later documentation answer points to the right project.

Trigger

New Task Created

Trigger when a new task is added to Todoist.

Action

Resolve-library-id

Resolves a package/product name to a Context7-compatible library ID and returns matching libraries. You MUST call this function before 'query-docs' to obtain a valid Context7-compatible library ID UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query. Selection Process: 1. Analyze the query to understand what library/package the user is looking for 2. Return the most relevant match based on: - Name similarity to the query (exact matches prioritized) - Description relevance to the query's intent - Documentation coverage (prioritize libraries with higher Code Snippet counts) - Source reputation (consider libraries with High or Medium reputation more authoritative) - Benchmark Score: Quality indicator (100 is the highest score) Response Format: - Return the selected library ID in a clearly marked section - Provide a brief explanation for why this library was chosen - If multiple good matches exist, acknowledge this but proceed with the most relevant one - If no good matches exist, clearly state this and suggest query refinements For ambiguous queries, request clarification before proceeding with a best-guess match. IMPORTANT: Do not call this tool more than 3 times per question. If you cannot find what you need after 3 calls, use the best result you have.

Why this helps

A short package name can match several projects, leading to confident but irrelevant answers.

  • Catches ambiguous names early
  • Improves follow-up query accuracy
  • Makes handoffs easier

Setup

Build it in a few focused steps.

  • 1Connect Todoist and Context7 MCP once in the Notis portal.
  • 2Create an automation that resolves ambiguous package names from each new task and reports the strongest Context7 matches.
  • 3Pick Todoist New Task Created as the trigger.
  • 4Choose a report channel and test with a task using a short or commonly reused package name.

Questions about this workflow

What should I do with the matches?

Confirm the intended library ID in the task or use the selected ID in a follow-up Query-docs automation.

Does it modify the Todoist task?

No. It reports the candidates so you can choose the correct project.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Todoist to Context7 MCP. A trigger fires from one place; an action lands in another.

Todoist triggers

Context7 MCP actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Query-docs

Retrieves and queries up-to-date documentation and code examples from Context7 for any programming library or framework. You must call 'resolve-library-id' first to obtain the exact Context7-compatible library ID required to use this tool, UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query. IMPORTANT: Do not call this tool more than 3 times per question. If you cannot find what you need after 3 calls, use the best information you have.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Resolve-library-id

Resolves a package/product name to a Context7-compatible library ID and returns matching libraries. You MUST call this function before 'query-docs' to obtain a valid Context7-compatible library ID UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query. Selection Process: 1. Analyze the query to understand what library/package the user is looking for 2. Return the most relevant match based on: - Name similarity to the query (exact matches prioritized) - Description relevance to the query's intent - Documentation coverage (prioritize libraries with higher Code Snippet counts) - Source reputation (consider libraries with High or Medium reputation more authoritative) - Benchmark Score: Quality indicator (100 is the highest score) Response Format: - Return the selected library ID in a clearly marked section - Provide a brief explanation for why this library was chosen - If multiple good matches exist, acknowledge this but proceed with the most relevant one - If no good matches exist, clearly state this and suggest query refinements For ambiguous queries, request clarification before proceeding with a best-guess match. IMPORTANT: Do not call this tool more than 3 times per question. If you cannot find what you need after 3 calls, use the best result you have.

ActionInstant

New Task Created

Trigger when a new task is added to Todoist.

TriggerPolling

Connect any two apps with Notis in the middle.

Todoist and Context7 MCP, or any other combination from 1,000+ integrations.

When this happens · Trigger

Do this · Action

Save your first hour today.

7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Context7 MCP.