Search: "lookups"

Queries 20+ bioinformatics resources through CLI/Python. Supports quick lookups of gene info, BLAST/BLAT, viral sequence downloads, PDB/mmCIF structures, G2P residue annotations, enrichment analysis, OpenTargets, COSMIC, CELLxGENE, and 8cube mouse specificity/expression data. Best for interactive exploration and simple queries. For batch processing or advanced BLAST use biopython; for multi-database Python workflows use bioservices.

Searches 18 scholarly APIs for papers, preprints, citations, open-access full text, repository records, and journal OA status, and returns results with reproducible provenance. Covers PubMed, PMC, Europe PMC, bioRxiv, medRxiv, arXiv, OpenAlex, Crossref, Semantic Scholar, CORE, Unpaywall, OpenCitations, PubTator3, Zenodo, Figshare, ROR, BioStudies, and DOAJ. Use when searching for papers, citations, DOI/PMID/arXiv lookups, abstracts, full text, open-access PDFs, preprints, citation graphs, author publications, biomedical entity annotations, deposited records (Zenodo, Figshare, BioStudies), institution ROR IDs, or any scholarly literature query. Triggers on mentions of any supported database or requests like "find papers on X", "look up this DOI", "who cites this paper", or "get me the PDF".

Uses Parallel CLI for web search, URL extraction, deep research, structured data enrichment, entity discovery, and recurring web monitoring. Best for requests that explicitly need current web evidence, academic-source discovery, repeated entity lookups, exhaustive reports, or ongoing change tracking.

Answer data questions -- from quick lookups to full analyses

Operating procedure for Adako, the MCP server and REST API that connects this assistant to the user's Google Ads, Meta Ads, LinkedIn Ads and ChatGPT Ads accounts (TikTok Ads tools are listed but not available yet). Use it whenever the user asks about ad spend, performance, campaigns, ad sets, ad groups, keywords, search terms, audiences, budgets, pixels, creatives, monitors or briefs on those platforms, and whenever they ask to create, pause, resume, re-budget or otherwise change anything in those accounts. It defines the safety contract (read before write, every write becomes a proposal the user approves, created objects are always paused), the tool-call contract (233 tools, read routers for lookups and _write routers for changes, ids are strings, budgets are decimals in the account currency, dates are YYYY-MM-DD or a preset), the tool map per platform, and the standard workflows for performance reviews, wasted-spend cleanup, campaign launches, monitors, approvals and error recovery. Do not use it for platforms Adako does not cover.

Operating procedure for Adako, the MCP server and REST API that connects this assistant to the user's Google Ads, Meta Ads, LinkedIn Ads and ChatGPT Ads accounts (TikTok Ads tools are listed but not available yet). Use it whenever the user asks about ad spend, performance, campaigns, ad sets, ad groups, keywords, search terms, audiences, budgets, pixels, creatives, monitors or briefs on those platforms, and whenever they ask to create, pause, resume, re-budget or otherwise change anything in those accounts. It defines the safety contract (read before write, every write becomes a proposal the user approves, created objects are always paused), the tool-call contract (233 tools, read routers for lookups and _write routers for changes, ids are strings, budgets are decimals in the account currency, dates are YYYY-MM-DD or a preset), the tool map per platform, and the standard workflows for performance reviews, wasted-spend cleanup, campaign launches, monitors, approvals and error recovery. Do not use it for platforms Adako does not cover.

Operating procedure for Adako, the MCP server and REST API that connects this assistant to the user's Google Ads, Meta Ads, LinkedIn Ads and ChatGPT Ads accounts (TikTok Ads tools are listed but not available yet). Use it whenever the user asks about ad spend, performance, campaigns, ad sets, ad groups, keywords, search terms, audiences, budgets, pixels, creatives, monitors or briefs on those platforms, and whenever they ask to create, pause, resume, re-budget or otherwise change anything in those accounts. It defines the safety contract (read before write, every write becomes a proposal the user approves, created objects are always paused), the tool-call contract (233 tools, read routers for lookups and _write routers for changes, ids are strings, budgets are decimals in the account currency, dates are YYYY-MM-DD or a preset), the tool map per platform, and the standard workflows for performance reviews, wasted-spend cleanup, campaign launches, monitors, approvals and error recovery. Do not use it for platforms Adako does not cover.