Render report text
render_report_textBuild a weekly client report from the same inputs as create_weekly_report and return it as plain text (header, accomplishments, hours, blockers, next week) ready to paste into an email or chat. Use when the user wants a readable report to send. Do NOT use when structured fields are needed; use create_weekly_report.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"client_name": "<client_name>",
"week_start": "<week_start>",
"accomplishments": "<accomplishments>"
},
"name": "render_report_text"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| blockers | No | Open issues blocking progress, one per entry, e.g. ["Waiting on API review"]. Default none. | |
| next_week | No | Planned tasks for next week, one per entry. Default none. | |
| week_start | Yes | First day of the reported week, YYYY-MM-DD (normally the Monday; use week_bounds to find it), e.g. 2026-09-28. The week ends 6 days later. | |
| client_name | Yes | Client the report is for, e.g. "Globex" | |
| hours_logged | No | Total hours worked this week, >= 0, e.g. 32. Omit if not tracked. | |
| accomplishments | Yes | What was done this week, one short item per entry (at least one), e.g. ["Shipped login", "Fixed 3 bugs"] |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | The weekly report rendered as multi-line plain text. |