ReportRaja

Create weekly report

create_weekly_report

Read-onlyIdempotent

Build a structured weekly client report (report ID, week start/end, accomplishments, hours, blockers, next-week plan) as data fields. Nothing is stored. Use when the report data will be processed or shown as fields. Do NOT use for a ready-to-send text version; use render_report_text.

Input Schema

Name	Required	Description
`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
`blockers`	Yes	Blockers (empty array if none).
`week_end`	Yes	Week end date, week_start + 6 days, YYYY-MM-DD.
`next_week`	Yes	Next-week plan items (empty array if none).
`report_id`	Yes	Report identifier, WR-YYYYMMDD-NNNN.
`week_start`	Yes	Week start date as given, YYYY-MM-DD.
`client_name`	Yes	Client name as given.
`hours_logged`	Yes	Hours logged, or null when not provided.
`accomplishments`	Yes	Accomplishments as given.

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedOct 10, 2026

changedInput schema / properties / accomplishments / description

Previous value: -"A list of accomplishments achieved during the week"New value: +"What was done this week, one short item per entry (at least one), e.g. [\"Shipped login\", \"Fixed 3 bugs\"]"

addedInput schema / properties / accomplishments / minItems
```
Added value: +1
```

changedInput schema / properties / blockers / description

Previous value: -"A list of issues or obstacles encountered during the week"New value: +"Open issues blocking progress, one per entry, e.g. [\"Waiting on API review\"]. Default none."

changedInput schema / properties / client_name / description

Previous value: -"The name of the client for whom the report is being generated"New value: +"Client the report is for, e.g. \"Globex\""

addedInput schema / properties / client_name / minLength
```
Added value: +1
```

changedInput schema / properties / hours_logged / description

Previous value: -"The total number of hours worked during the week"New value: +"Total hours worked this week, >= 0, e.g. 32. Omit if not tracked."

addedInput schema / properties / hours_logged / minimum
```
Added value: +0
```

changedInput schema / properties / next_week / description

Previous value: -"A list of tasks planned for the next week"New value: +"Planned tasks for next week, one per entry. Default none."

changedInput schema / properties / week_start / description

Previous value: -"The start date of the week in YYYY-MM-DD format"New value: +"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."

addedInput schema / properties / week_start / pattern
```
Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "accomplishments": {
+      "description": "Accomplishments as given.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "blockers": {
+      "description": "Blockers (empty array if none).",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "client_name": {
+      "description": "Client name as given.",
+      "type": "string"
+    },
+    "hours_logged": {
+      "description": "Hours logged, or null when not provided.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "next_week": {
+      "description": "Next-week plan items (empty array if none).",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "report_id": {
+      "description": "Report identifier, WR-YYYYMMDD-NNNN.",
+      "type": "string"
+    },
+    "week_end": {
+      "description": "Week end date, week_start + 6 days, YYYY-MM-DD.",
+      "type": "string"
+    },
+    "week_start": {
+      "description": "Week start date as given, YYYY-MM-DD.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "report_id",
+    "client_name",
+    "week_start",
+    "week_end",
+    "accomplishments",
+    "hours_logged",
+    "blockers",
+    "next_week"
+  ],
+  "type": "object"
+}

Changed1 schema field changedOct 10, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "accomplishments": {
-      "description": "List of accomplishments for the week.",
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "blockers": {
-      "description": "List of blockers encountered during the week.",
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "client_name": {
-      "description": "The name of the client for whom the report is generated.",
-      "type": "string"
-    },
-    "hours_logged": {
-      "description": "Total hours logged for the week.",
-      "type": "number"
-    },
-    "next_week": {
-      "description": "List of plans for the next week.",
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "report_id": {
-      "description": "Unique identifier for the generated report.",
-      "type": "string"
-    },
-    "report_text": {
-      "description": "The formatted text of the weekly report.",
-      "type": "string"
-    },
-    "week_start": {
-      "description": "The start date of the week for which the report is generated.",
-      "type": "string"
-    }
-  },
-  "required": [
-    "report_id",
-    "client_name",
-    "week_start",
-    "accomplishments",
-    "report_text"
-  ],
-  "type": "object"
-}New value: +null

Changed7 schema fields changedOct 6, 2026

addedInput schema / properties / accomplishments / description

Added value: +"A list of accomplishments achieved during the week"

addedInput schema / properties / blockers / description

Added value: +"A list of issues or obstacles encountered during the week"

addedInput schema / properties / client_name / description

Added value: +"The name of the client for whom the report is being generated"

addedInput schema / properties / hours_logged / description

Added value: +"The total number of hours worked during the week"

addedInput schema / properties / next_week / description

Added value: +"A list of tasks planned for the next week"

addedInput schema / properties / week_start / description

Added value: +"The start date of the week in YYYY-MM-DD format"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "accomplishments": {
+      "description": "List of accomplishments for the week.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "blockers": {
+      "description": "List of blockers encountered during the week.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "client_name": {
+      "description": "The name of the client for whom the report is generated.",
+      "type": "string"
+    },
+    "hours_logged": {
+      "description": "Total hours logged for the week.",
+      "type": "number"
+    },
+    "next_week": {
+      "description": "List of plans for the next week.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "report_id": {
+      "description": "Unique identifier for the generated report.",
+      "type": "string"
+    },
+    "report_text": {
+      "description": "The formatted text of the weekly report.",
+      "type": "string"
+    },
+    "week_start": {
+      "description": "The start date of the week for which the report is generated.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "report_id",
+    "client_name",
+    "week_start",
+    "accomplishments",
+    "report_text"
+  ],
+  "type": "object"
+}

First observedOct 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds a genuinely non-redundant behavioral fact — 'Nothing is stored' — clarifying this is a pure computation with no persistence, which the annotations do not convey. It stops short of noting any auth or rate-limit behavior, so it is strong but not exhaustive.

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

Conciseness5/5

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

Three sentences, front-loaded with the core action and output shape, followed by the usage condition and the negative routing. No filler, no repetition of schema detail.

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

Completeness5/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 described, and the description covers purpose, field structure, persistence behavior, and sibling routing. For a 6-parameter creation tool with full schema coverage, nothing an agent needs to call it correctly is 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%: every parameter has its own description with format, examples, and defaults (e.g. week_start pattern and 'use week_bounds to find it', hours_logged 'Omit if not tracked'). The description only restates the field list, adding no syntax or format meaning beyond the schema, so the baseline of 3 applies.

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

Purpose5/5

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

States a precise verb+resource ('Build a structured weekly client report') and enumerates the exact fields produced (report ID, week start/end, accomplishments, hours, blockers, next-week plan). It also explicitly distinguishes itself from the sibling render_report_text, so an agent can choose without opening either schema.

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

Usage Guidelines5/5

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

Gives both a positive trigger ('Use when the report data will be processed or shown as fields') and an explicit exclusion with the alternative named ('Do NOT use for a ready-to-send text version; use render_report_text'). This is textbook when/when-not/alternative guidance.

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

All ReportRaja tools Inspect

Try in Browser

Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Create weekly report

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources