notebook-dossier

Overview Schema Source Related Servers Discussions Admin

Dossier Result

dossier_result

Retrieve paginated research results by view—findings, report, digest, evidence, comparisons, tasks, or answers—for a specified research_id.

Instructions

findings 为完整发现来源（含 cite_map、citation_warnings、逐来源提取式摘要）； report 为报告全文分页（cursor=字符偏移、max_chars=窗口）； digest 为提取式执行摘要（≤1500 字 + 高被引来源清单）； include_report_text 仅作用于 findings 视图的报告内嵌（旧口径，建议改用 view='report'）。

Input Schema

Name	Required	Default
`view`	No	findings
`limit`	No
`cursor`	No
`max_chars`	No
`research_id`	Yes
`include_report_text`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.0.1Oct 23, 2026
- addedInput schema / properties / max_chars
```
Added value: +{
+  "default": 12000,
+  "type": "integer"
+}
```
First observedv0.1.0Oct 20, 2026

TDQS

A3.6/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden; it discloses pagination behavior, view-specific contents such as cite_map and citation_warnings, report cursor/max_chars semantics, the digest length cap, and the deprecated include_report_text behavior. Remaining gaps include default pagination behavior and whether limit/cursor apply consistently across all views.

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

Conciseness4/5

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

The description is front-loaded with purpose and the view list, then adds useful view-specific details and a deprecation note. It is dense but efficient, with little wasted text.

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

Completeness3/5

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

The output schema exists, so return values need not be fully explained, but the tool still has 6 parameters, 0% schema descriptions, no annotations, and seven view values of which four are undocumented. The description is adequate for the main views but incomplete for the full tool surface.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must compensate. It explains view, cursor, max_chars, and include_report_text to some extent, but only details findings/report/digest; it leaves evidence, comparisons, tasks, answers, and the limit parameter without semantic guidance.

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

Purpose4/5

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

States a specific verb and resource: paginated reading of research results, with a list of supported views. The scope is clear, but it does not explicitly distinguish this tool from siblings such as dossier_evidence, dossier_compare, or dossier_query.

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

Usage Guidelines3/5

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

Provides implied guidance by describing findings as the complete source, report as full-text pagination, and digest as a summary, plus a recommendation to use view='report' instead of include_report_text. However, it gives no when-to-use guidance for the other view values or for choosing this tool over sibling tools.

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

Deploy Server