AnswerThis
AnswerThis v0.1.4
Research with cited evidence.
From the developer
Declared capabilities
- Read
- Write
Cost & access
The connector does not sell products or process payments. An existing AnswerThis account and applicable usage credits are required for account and processing tools.
Declared limitations
- Private library access requires an authenticated account; no private data may be returned before sign-in.
- Identifiers belonging to a different user do not authorize reading or writing their records.
- Library-folder deletion and attaching an exported PDF are not exposed MCP operations.
Onboarding example
Review the literature on my research question.
Sources & dates
Developer declarations; not independently tested. Listing last checked Nov 11, 2026. Package observed Nov 10, 2026.
Description
From the marketplace listing
Search scholarly literature, inspect available full text, compare evidence, and find research gaps. Researchers can connect their AnswerThis account to read and save library papers, create and edit cited Writer drafts, and run screening, extraction, and persistent reviews. Public search is available without an account; account tools require sign-in and the relevant permissions. Source availability varies.
Language: English · Automatically detected from descriptions.
Changes
No changes recorded yet. Follow this plugin to keep track of future changes.
First seen Nov 10, 2026. Last seen Nov 11, 2026.
Similar plugins
Find competitors to follow as you develop your plugin.
-
Lexiara helps users search EU and UK legislation, retrieve provision-level text with source provenance, trace amendments and transpositio...
Shared terms: cited, research, text, source
-
Search U.S. statutes, regulations, rules, case law, and EEOC and NLRB decisions in Paxton, read source text, and check case citation hist...
Shared terms: cited, research, inspect, permission
-
Research historical civic meetings using metadata and stored transcript search, source retrieval, and cited briefs with coverage limitati...
Shared terms: cited, research, varie, inspect
-
Full-text, peer-reviewed scientific and medical literature, licensed from publishers and drawn from open-access journals, searched as one...
Shared terms: research, literature, paper, relevant
-
Search scholarly literature and organize research in Wisebase.
Shared terms: research, literature, paper, scholarly
Keywords
Files & skills
File archives
Skill instructions
literature-review3.38 KB
--- name: literature-review description: Synthesize a literature review with AnswerThis paper discovery and retrieved evidence, comparing methods, findings, contradictions, and retrieval limits. --- Build a review around the user's research question and the evidence retrieved in this conversation. For library papers, locate the requested folder with `list_library_folders`, browse it with `list_library_papers`, and use `read_library_paper`. Save newly discovered papers only when the user requests it; otherwise use their available abstracts and evidence. Reading missing library text requires permission to acquire and store the PDF. Follow `next_offset` with the same `version` until every page is read. Identify abstract-only findings and inaccessible papers. 1. Define the question's population, methods, outcomes and timeframe where relevant. Plan the terms and synonyms for each facet. State any scope assumption that affects inclusion. 2. Inspect the available AnswerThis tools and their current input schemas. Use `search_papers` to discover papers and resolve identifiers. Use `get_evidence_passages`, when available, to retrieve citable evidence. Request account connection if the tool requires it, then resume the same task. Use the host's registered tool names even when they include a plugin prefix. 3. Cover the question from several relevant angles. Start with recent reviews to map terminology, then retrieve primary research for measured effects and study methods. Retry a search when a missing facet has a concrete new query or source to try. Record uncovered facets as retrieval limits. 4. Maintain an evidence table with paper identity, study design, population, relevant finding and the passage that supports it. Mark information that the returned evidence does not provide. `get_evidence_passages` currently returns abstracts, not full papers; report that reading limit and avoid claims about inaccessible sections. 5. Write the review around comparisons across studies. Separate primary studies from reviews, explain disagreements and methodological differences, and distinguish supported conclusions from your interpretation. An empty search cannot establish that research does not exist. 6. Use APA unless the user requests another supported `citation_style`. Pass it to `search_papers`, `get_evidence_passages`, and `list_library_papers`. In chat, pair returned `citation.inline` citations with `citation.full` bibliography entries and source URLs or DOIs. Keep raw citation IDs out of chat. For requested Writer saves or edits, use exact citation markers in `create_draft` or `update_draft` Markdown and supply the original evidence `context_ids`, including earlier searches. Leave references unlinked when no URL is available. Reconcile numbered citations across searches with a consistent paper-to-number mapping. 7. End with supported conclusions and the remaining uncertainties. In chat, include a bibliography of sources actually used. Save to AnswerThis through `create_draft` only when requested, following its prose-and-linked-citations contract so Writer generates the exported bibliography. Then offer the returned document link. Deliver the review in the conversation unless the user requests a file or saving to AnswerThis. If an import/editing tool is available, inspect its schema and use it only for the requested save or edit. A local draft or host-generated answer has not automatically been saved in AnswerThis.
research-gaps3.16 KB
--- name: research-gaps description: Identify evidenced research gaps with AnswerThis, test proposed gaps against contrary findings, and propose specific follow-up studies. --- Produce a map of supported open questions in the user's field. A low search count is a retrieval result, not a research gap. For library papers, locate the requested folder with `list_library_folders`, browse it with `list_library_papers`, and use `read_library_paper`. Save newly discovered papers only when the user requests it; otherwise use their available abstracts and evidence. Reading missing library text requires permission to acquire and store the PDF. Follow `next_offset` with the same `version` until every page is read. Identify abstract-only findings and inaccessible papers. 1. Break the topic into relevant populations, interventions, methods, outcomes and settings. List synonyms and narrower concepts before searching. 2. Inspect the available AnswerThis tool schemas. Discover papers with `search_papers` and retrieve citable passages with `get_evidence_passages` when it is available. Use the host's registered names, including plugin prefixes. If account connection is required, connect and continue the research task. 3. Retrieve recent reviews and primary studies that state limitations, unanswered questions or future work. For each proposed gap, search directly for work that may already address it. If contrary evidence exists, revise or reject the proposed gap. 4. Build each gap from an explicit source statement or a documented contradiction between retrieved studies. Cite both sides of a contradiction. A passage reporting a positive finding does not support an attached claim that other work is absent. Current `get_evidence_passages` evidence is abstract-only; do not imply full-text review. 5. For each supported gap, explain what is established, what is missing or disputed, why resolving it matters, and one feasible research question or design. Separate the authors' stated limitation from your proposed next study. 6. Order gaps by strength of evidence and practical value. If evidence cannot establish a proposed gap, describe the retrieval limitation instead of presenting it as an open problem in the field. 7. Use APA unless the user requests another supported `citation_style`. Pass it to `search_papers`, `get_evidence_passages`, and `list_library_papers`. In chat, pair returned `citation.inline` citations with `citation.full` bibliography entries and source URLs or DOIs. Keep raw citation IDs out of chat. For requested Writer saves or edits, use exact citation markers in `create_draft` or `update_draft` Markdown and supply the original evidence `context_ids`, including earlier searches. Leave references unlinked when no URL is available. Reconcile numbered citations across calls and include only sources used. Follow the Writer tool's prose-and-linked-citations contract and return its document link. If `get_evidence_passages` is unavailable, clearly limit the output to what retrieved metadata or abstracts support. Never invent passages, citation identifiers, studies, or an AnswerThis saved result. A suggested research direction is a proposal, not proof that the study has never been done.
Release notes
Version 0.1.4 clarifies the existing 39-tool directory submission without changing server behavior. The DOI lookup scenario explicitly discloses the known Lost in the Middle catalogue/preprint-year discrepancy; the Writer scenario uses owned library full-text citation contexts and reads back the saved document; screening and extraction share a 100-credit aggregate cap. The package retains mixed public/OAuth access, five positive plus three negative reviewer scenarios, the demonstration recording, and connector privacy, terms and setup pages.
Declared in the saved package. Remote tools may change independently.
Package details
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
- Package author
- AnswerThis
- Keywords
- See keywords
- Commerce declaration
- Does not support commerceThis does not establish whether access is free or paid.
- Review scenarios
- 5 positive · 3 negativeScenario counts, not test results.
Declared capabilities
- Read
- Write
Package observed Nov 10, 2026.
Technical details
- First seen
- Nov 10, 2026 · 12:00 UTC
- Last seen
- Nov 11, 2026 · 06:00 UTC
- Collection status
- Collected
plugin_asdk_app_6adaa2fd86a08191ac4186768186c1a9
Download plugin data (JSON)Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.