Skip to main content
Glama

ReportRaja

by io.github.everyai-com
OverviewDiscussionsAdmin

Week bounds

week_bounds
Read-onlyIdempotent

Return the Monday-to-Sunday week containing a given date (UTC). Use to turn a date like 'Oct 2' into the week_start for a report. Do NOT use to build the report itself; use create_weekly_report or render_report_text.

Input Schema

NameRequiredDescriptionDefault
dateYesAny date in the week, YYYY-MM-DD, e.g. 2026-10-02

Output Schema

NameRequiredDescriptionDefault
week_endYesSunday of that week, YYYY-MM-DD.
week_startYesMonday of that week, YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / date / description
      Previous value: -"The date in YYYY-MM-DD format."New value: +"Any date in the week, YYYY-MM-DD, e.g. 2026-10-02"
    • addedInput schema / properties / date / pattern
      Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "week_end": {
+      "description": "Sunday of that week, YYYY-MM-DD.",
+      "type": "string"
+    },
+    "week_start": {
+      "description": "Monday of that week, YYYY-MM-DD.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "week_start",
+    "week_end"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "endDate": {
-      "description": "The end date of the week (Sunday) in YYYY-MM-DD format.",
-      "type": "string"
-    },
-    "startDate": {
-      "description": "The start date of the week (Monday) in YYYY-MM-DD format.",
-      "type": "string"
-    }
-  },
-  "required": [
-    "startDate",
-    "endDate"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed2 schema fields changed
    • addedInput schema / properties / date / description
      Added value: +"The date in YYYY-MM-DD format."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "endDate": {
+      "description": "The end date of the week (Sunday) in YYYY-MM-DD format.",
+      "type": "string"
+    },
+    "startDate": {
+      "description": "The start date of the week (Monday) in YYYY-MM-DD format.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "startDate",
+    "endDate"
+  ],
+  "type": "object"
+}
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, providing safety profile. The description adds the crucial UTC timezone context, which affects behavior. However, it doesn't describe output format or edge cases (e.g., handling of invalid dates), so it's not fully complete.

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?

Two sentences, zero waste. The core purpose is front-loaded, followed by usage guidance and exclusions. Every sentence earns its place.

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?

A complete definition for a simple, single-parameter tool with full schema coverage and annotations. The presence of an output schema means return values need not be detailed. The description covers purpose, usage, and exclusion cases adequately.

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 coverage is 100%, so the schema fully documents the single parameter (date with format and example). The description mentions 'given date (UTC)' but adds no syntactic or semantic details beyond what the schema provides. Baseline 3 is appropriate.

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 specific verb ('return'), resource ('Monday-to-Sunday week'), and scope ('containing a given date (UTC)'). The description clearly distinguishes this tool from siblings by naming create_weekly_report and render_report_text.

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?

Explicitly states when to use ('turn a date like 'Oct 2' into the week_start for a report') and when not to ('Do NOT use to build the report itself'), naming alternative tools. This leaves no ambiguity for an agent.

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

All ReportRaja toolsInspect
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.

Resources