Skip to main content
Glama
talenlin

notebook-dossier

by talenlin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Dossier Status

dossier_status

Checks a research task's status and returns the full report with discovered sources, plus phase, elapsed time, and suggested next poll interval.

Instructions

查询研究任务状态，并同步完整报告与发现来源清单。

完成时会保存 compact=False 的完整结果；来源统计与发现/导入不是同一指标。 返回 phase/elapsed_ms/sources_discovered 与自适应 suggested_next_poll_seconds。

Input Schema

NameRequiredDescriptionDefault
research_idYes研究任务 ID。
wait_secondsNo>0 时服务端长轮询（封顶 300s）：阻塞到状态变化或超时，把 N 次轮询压成 1 次调用。

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.0.1
    • addedInput schema / properties / research_id / description
      Added value: +"研究任务 ID。"
    • addedInput schema / properties / wait_seconds
      Added value: +{
+  "default": 0,
+  "description": ">0 时服务端长轮询（封顶 300s）：阻塞到状态变化或超时，把 N 次轮询压成 1 次调用。",
+  "type": "number"
+}
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

No annotations, so the description carries the full burden and rises to it partly: it discloses that completion persists the full compact=False result and warns that source statistics is not the same metric as discovery/import. It omits auth requirements, error behavior, or rate limits beyond the long-poll cap already in the schema.

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?

Four compact sentences, front-loaded with the core purpose before the completion-save and metrics caveats. Each sentence carries information, with no repetition of schema content.

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

Completeness4/5

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

An output schema exists, so return values need not be explained, yet the description usefully foreshadows phase/elapsed_ms/sources_discovered and the adaptive poll hint. For a two-param status tool with full schema coverage, this is sufficient, with only permission and failure-mode context missing.

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 100%, including the wait_seconds long-poll semantics, so the schema does the parameter work. The description adds no parameter-level meaning beyond what the schema already provides; baseline 3 is appropriate.

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: querying research task status, plus syncing the full report and the list of discovered sources. It is clear enough to separate it from dossier_result, which returns the finished result, but the description never names the sibling, so differentiation is implied rather than stated.

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?

There is no explicit when-to-use or when-not-to-use guidance, nor a named alternative among the many siblings. Usage is only implied by the mention of suggested_next_poll_seconds, which signals this tool is meant for polling.

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

Deploy Server

Other Tools