Files

T

2026-09-28 16:17:05 +03:00

name, description, metadata

name	description	metadata
shd-active-projects	Use when the user asks for all active SHD projects, project deadlines, project statuses, or a project register sorted by the nearest completion date.	modules=projects-core

SHD active projects

Workflow

Call shd_list_projects once with archived: false and limit: 100.
If the user supplied a search term, pass it as q; otherwise do not add a search filter.
Use the project fields returned by that tool. Do not call shd_get_project once per row just to repeat list data.
Sort projects with a non-null deadline in ascending order. Put projects without a deadline after dated projects; do not invent a date.
If the user is in a UI-capable MCP host, call shd_render_projects_widget after the data call, passing the returned data array as projects and the returned meta object as meta. When rendering succeeds, keep the project rows inside the widget and give only a short confirmation in the final response; do not repeat the rows as prose or a Markdown table.
If the UI host is unavailable or the render tool returns an error, return the compact fallback table:

Проект | Дата завершения | Статус
Preserve the server's project name/code and status. If a deadline is a datetime, format it with its returned timezone when available; otherwise keep the value unmodified and state that timezone data was unavailable.

“Активные” defaults to non-archived projects (archived: false). If the user means a particular business status rather than archive state, ask which status or report the returned statuses without filtering them locally.
Do not use task due dates as project completion dates.
If the server indicates more records than the tool can return, report that the current tool limit was reached; do not claim a complete list.
This workflow is read-only and must not update, archive or delete projects.

See references/project-widget.md for the data/render boundary.