1.5 KiB
1.5 KiB
name, description, metadata
| name | description | metadata |
|---|---|---|
| shd-analytics | Use when the user asks for SHD project or company analytics, trends, comparisons, metrics, charts, reports, or time summaries. | modules=* |
SHD analytics and reports
Scope
- Resolve the organization or project scope before aggregating values. Use an
exact
project_codewhen the user supplied one; otherwise resolve it withshd_list_projects. - Use
shd_get_project_contextfor a bounded cross-module summary and request only the sections needed for the question. - For task effort use
shd_get_task_time_report; useshd_export_task_time_reportonly when the user asks for an export. - For proposal analytics use
shd_get_proposal_public_analyticsonly for a resolved proposal or public analytics scope accepted by its schema. - If the requested metric does not map to a known tool, call
shd_capabilitiesand report the unavailable capability instead of inventing an endpoint or field.
Reporting rules
- State the period, scope, currency and timezone returned by SHD.
- Distinguish totals returned by the server from calculations made from rows.
- Preserve null, unavailable and permission-denied sections as separate states.
- Do not infer profitability, completion, approval or trend direction from one record or from a missing section.
- Present chart-ready data as a compact table with labels, units and source fields. Use a UI resource only when the server advertises a matching widget.
See references/analytics-contract.md before composing a multi-section report.