Skip to main content
Glama
Wang-JQ77

deepseek-litresearch

by Wang-JQ77

deep_research

Generates cited, evidence-graded scientific research reports by recursively searching multiple academic databases, using an outline-first workflow to confirm structure before synthesis and critical review.

Instructions

对科学问题进行深度调研,返回带引用的 Markdown 报告(大纲先行)。

内部执行 规划→并行检索→粗排→提炼→反思→综合 的递归循环。

大纲先行(默认):先生成调研大纲并返回(status=planned + job_id + plan), 供用户确认或修改;确认后调用 execute_research(job_id, plan_override=...) 继续执行。 传 confirm_outline=false 或关闭设置 litresearch.outline_first,则一次调用跑完 完整流水线(直达模式)。执行期间进度写入 progress/.json,前端展示进度条。

Args: question: 科学问题(如 "GLP-1 receptor agonists in neurodegenerative diseases")。 breadth: 规划阶段拆分的子问题数(1-6,默认取设置里的广度)。 depth: 递归检索深度(1-3,默认取设置里的深度)。 max_papers: 文献池规模上限(默认 50)。 sources: 数据源列表,默认全部可用源。 format: 报告导出格式,markdown | html | both | json(默认 markdown)。 导出文件写入 DRS_REPORT_DIR,返回 report_paths + cost 成本摘要。 critique: 是否启用红队对抗审查(M8,默认 True;规则审查 + LLM 可用时 LLM 审查)。 track: 是否持久化任务到 SQLite(M10,默认 True),返回 job_id 供后续查询。 language: 报告语言(M11),zh | en(默认 zh)。 confirm_outline: 大纲先行开关(默认取设置 litresearch.outline_first)。 true=只生成大纲返回等确认;false=一次跑完直达报告。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
depthNo
trackNo
formatNomarkdown
breadthNo
sourcesNo
critiqueNo
languageNozh
questionYes
max_papersNo
confirm_outlineNo
Install Server

TDQS

A5/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

无 annotations,但描述完整披露了内部流水线、大纲先行/直达模式、进度文件写入、导出文件目录、SQLite 持久化、cost 摘要和红队审查默认开启等行为。对调用者可预见的副作用和状态变化说明充分。

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

开篇用一句话概括目的,内部流程、执行模式、参数列表分层清晰,信息密度高。对 10 参数、双执行路径的复杂工具来说,长度合理且没有冗余内容。

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

无 output schema,但描述已覆盖返回值(status=planned + job_id + plan、report_paths + cost)、进度文件、导出文件、SQLite 跟踪及后续 execute_research 调用方式。对高复杂度工具而言上下文完整,足以让 agent 正确选择和调用。

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

schema_description_coverage 为 0%,但描述对全部 10 个参数逐一补充了语义、范围、默认值和行为影响,如 breadth 1-6、depth 1-3、max_papers 50、format 枚举及 confirm_outline 开关。这远超 schema 本身提供的信息量。

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

描述明确了核心用途:对科学问题进行深度调研并返回带引用的 Markdown 报告。通过'大纲先行'、直达模式和调用 execute_research 的说明,有效将 deep_research 与 plan_research、execute_research 等兄弟工具区分开。

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

清楚说明了两种使用路径:默认生成大纲等待用户确认后用 execute_research 继续,或设置 confirm_outline=false 一次跑完。还说明进度文件与 job_id 的用途,对何时调用本工具、何时转交 execute_research 给出了明确指引。

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Wang-JQ77/dsh-litresearch'

If you have feedback or need assistance with the MCP directory API, please join our Discord server