Skip to main content
Glama
Sign In
Commonpost MCP for Thunderbird

Commonpost MCP for Thunderbird

by commonpost
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
JavaScript
Local

List Tasks

listTasks
Read-onlyIdempotent

Lists to-dos from all or one Thunderbird task calendar, sorted by due date, with optional completed and due-before filters. Use it to review open or completed tasks before updating them.

Instructions

List tasks (to-dos) from all task calendars or one, sorted by due date (undated last, by title); at most maxResults, no paging. Rows: id, calendarId, title, dueDate, startDate, completed, completedDate, percentComplete, priority (1 high, 5 normal, 9 low), description. To change one, updateTask; events: listEvents.

Input Schema

NameRequiredDescriptionDefault
formatNo'table' returns { columns, rows }
reviewIdNoFrom createTask: that dialog's state instead (open, saved + taskId, closed unsaved, failed)
completedNotrue: completed only, false: open only; omit for all
dueBeforeNoReturn tasks due before this ISO 8601 date
calendarIdNoCalendar ID (from listCalendars); omit for all
maxResultsNoMax tasks

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / reviewId
      Added value: +{
+  "description": "From createTask: that dialog's state instead (open, saved + taskId, closed unsaved, failed)",
+  "type": "string"
+}
  2. Changed2 schema fields changedv0.19.2
    • changedInput schema / properties / calendarId / description
      Previous value: -"Calendar ID to query (from listCalendars). If omitted, queries all task-capable calendars."New value: +"Calendar ID (from listCalendars); omit for all"
    • changedInput schema / properties / completed / description
      Previous value: -"Filter by completion status. true = completed only, false = outstanding only. Omit for all tasks."New value: +"true: completed only, false: open only; omit for all"
  3. First observedv0.1.0

TDQS

A4.7/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 behavior. The description adds useful behavioral detail beyond that: due-date sorting with undated last, no paging, and the exact row fields including priority encoding.

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 description is dense but front-loaded: sorting, result cap, returned row fields, and sibling routing are packed into three semicolon-separated clauses without 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?

There is no output schema, so the description supplies the return shape via the row field list and priority mapping, and it also discloses sorting and no-paging behavior. This is complete for a read-only list tool.

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%, so the schema already documents each parameter. The description reinforces the maxResults cap and all-calendars scope but does not add per-parameter meaning for completed, dueBefore, format, or reviewId beyond what the schema provides.

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?

Opens with a specific verb and resource ('List tasks (to-dos)'), states the scope ('from all task calendars or one'), and clearly distinguishes this read operation from updateTask and listEvents.

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?

Explains that omitting calendarId covers all calendars, that results are capped at maxResults with no paging, and explicitly routes modifications to updateTask and events to listEvents.

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