Skip to main content
Glama

Get week

get_week
Read-onlyIdempotent

Read the user's Weeklane plan for 7 days, grouped by day. Use this first when the user talks about their week, wants a plan, or asks what is coming up. Without startDayKey it returns the current week (starting on the user's first weekday). For "next week", or when today is the last day of the week, pass startDayKey. Results include today's date and the user's time zone. Occurrences of repeating tasks have repeats + repeatingTaskId.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_week"
  }
}

Input Schema

NameRequiredDescriptionDefault
startDayKeyNoFirst day to show ("YYYY-MM-DD" or "today"). Omit for the current week.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely new behavioral facts: the omission default is the current week anchored to the user's first weekday, results carry today's date and time zone, and repeated tasks come back with repeats plus repeatingTaskId. With no output schema, these return-shape disclosures carry real weight.

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?

Four compact sentences, ordered by importance: what it returns, when to use it, default behavior, then the special-case parameter rule and return notes. Nothing is redundant with the schema or the annotations.

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?

For a single-optional-parameter read tool with no output schema, the description covers purpose, routing, default behavior, parameter edge case, and the shape of the returned data including repeating-task metadata. An agent has everything needed to select and invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents the format and the omit behavior; the description adds the reasoning behind passing startDayKey ('next week', or when today is the last day of the week), which is meaning beyond the field spec. It stops short of adding format edge cases, so it is not a 5.

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?

The opening sentence gives a specific verb and resource ('Read the user's Weeklane plan') plus scope ('for 7 days, grouped by day'), which is enough to separate it from the task-level siblings like list_tasks or search_tasks without opening a 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?

It states explicitly when to reach for this tool ('Use this first when the user talks about their week, wants a plan, or asks what is coming up') and gives concrete conditions for the parameter ('For "next week", or when today is the last day of the week, pass startDayKey'), which is unusually actionable routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources