Skip to main content
Glama
Sign In
mcp-google-workspace

mcp-google-workspace

by guinacio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Tasks Digest

tasks_tasks_digest
Read-onlyIdempotent

Triage open tasks in a Google Tasks list—default or specified—into overdue, upcoming, and unscheduled groups to prioritize work within a lookahead window.

Instructions

Triage one task list's open tasks into overdue, upcoming and unscheduled work; it reads the default list unless tasklist_id names another one from tasks_list_tasklists. For completed tasks or custom filters use tasks_list_tasks. Returns overdue (due before today in the account time zone), upcoming (due from today through the window, soonest first) and unscheduled (no due date), each a list of tasks shaped as in tasks_list_tasks, plus count (tasks in the three groups), tasklist_id (the list's real ID when Google reports it), window_days and account_timezone.

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": "tasks_tasks_digest"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoDays ahead of today whose due tasks go in 'upcoming'; tasks due later appear in no group.
max_resultsNoMaximum open tasks to read from the list, 1 to 100; there is no paging, so tasks past this are left out.
tasklist_idNoTask list ID from tasks_list_tasklists; omit for the account's default list.

Output Schema

NameRequiredDescriptionDefault
countNoNumber of items in this response.
overdueNo
has_moreNoWhether another page is available.
upcomingNo
fetched_atNoRFC3339 time when this response was fetched.
tasklist_idNo
unscheduledNo
window_daysNo
next_page_tokenNoOpaque token for the next page, or null.
account_timezoneNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior. The description adds operational context beyond that: the grouping semantics, time-zone handling, sorting of 'upcoming', truncation behavior via max_results in the schema, and the exact shape of returned groups and counts.

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?

The purpose is front-loaded, followed immediately by the alternative tool and then the return-value contract. The text is dense but every sentence carries information needed to select and interpret the tool; there is no filler.

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 read-only digest with a full input schema, annotations, and an output schema, the description is complete. It explains grouping, default-list behavior, alternative tool routing, sorting, time zone, and output structure without over-explaining fields already covered elsewhere.

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 coverage is 100%, so the schema carries most parameter meaning. The description still adds value by tying 'days' to the 'upcoming' group and clarifying that upcoming results are sorted soonest first, though it does not elaborate on max_results truncation beyond what the schema already says.

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 description opens with a specific verb and scope: 'Triage one task list's open tasks into overdue, upcoming and unscheduled work.' It explicitly distinguishes this digest from a general filtered-list tool by naming tasks_list_tasks for completed tasks or custom filters.

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 the default behavior ('reads the default list unless tasklist_id names another one') and names the alternative tool for different needs ('For completed tasks or custom filters use tasks_list_tasks'). This leaves little ambiguity about when to call this digest versus a task-list tool.

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

Deploy Server

Other Tools