Skip to main content
Glama
andreasd083

amazing-marvin-complete-mcp

by andreasd083
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_today_items

Read-only

Get open tasks and projects scheduled today or earlier. Open tasks/projects with day <= the date (default today in the configured timezone, MARVIN_TIMEZONE), not only exactly on the date. Deadline-only items: get_due_items.

Instructions

Get open tasks and projects scheduled today or earlier. Open tasks/projects with day <= the date (default today in the configured timezone, MARVIN_TIMEZONE), not only exactly on the date. Deadline-only items: get_due_items. Filters as the app does: for a recurring task with If you miss one = Keep just one (carry) only the oldest open occurrence is shown, for Only the current one (skip) only the date's own; Keep them all and the account default ('', assumed to be Keep them all) show all. The mode is read (/doc) only for recurring tasks with an open occurrence before today, cached until local midnight; a mode changed in the app takes effect by the next day at the latest. If the mode cannot be read the occurrences are shown. The response gives hidden_count and which were hidden; include_hidden=true includes all. Habit tasks (field habitId) are listed in habit_task_ids. Recurring occurrences are created the first time a Marvin client opens after the day rolls over; read before that, today's occurrences are missing, and a recurring task created during the day may lack them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate YYYY-MM-DD; returns everything open with day <= the date; omit for today (MARVIN_TIMEZONE, else the system timezone)
include_hiddenNoTrue = include occurrences the app hides (If you miss one)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.7.3
    • addedInput schema / properties / include_hidden
      Added value: +{
+  "default": false,
+  "description": "True = include occurrences the app hides (If you miss one)",
+  "type": "boolean"
+}
  2. Changed1 schema field changedv1.6.0
    • changedInput schema / properties / date / description
      Previous value: -"Date YYYY-MM-DD; omit for today (server timezone)"New value: +"Date YYYY-MM-DD; returns everything open with day <= the date; omit for today (MARVIN_TIMEZONE, else the system timezone)"
  3. First observedv1.3.0

TDQS

A4.6/5.0
Behavior5/5

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

Much richer than the readOnlyHint/openWorldHint annotations: it discloses recurrence filtering modes (carry/skip/keep all), that the mode is read/cached until local midnight, the fallback when the mode can't be read, and the significant caveat that occurrences are only created once a client opens after the day rolls over. This is exactly the kind of behavior an agent could not infer from structured fields.

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

Conciseness4/5

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

The core purpose and scope constraint are front-loaded, and every paragraph carries information the agent needs. It is dense and unstyled, with the recurring-mode sentence bordering on implementation detail, but nothing is truly wasted.

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, yet the description still explains the notable return fields (hidden_count, which items were hidden, habit_task_ids) and the timing caveat about missing occurrences. For a read tool with a filtering quirk, nothing an agent needs is missing.

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 baseline is 3, but the description adds real meaning: it ties include_hidden to the app's hiding modes and reinforces the 'day <= date' semantics of the date parameter beyond the schema wording, so the agent understands the interaction between the two params.

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 and resource ('Get open tasks and projects scheduled today or earlier') and immediately clarifies the subtle scope ('day <= the date, not only exactly on the date'). It also names the sibling that covers the other case ('Deadline-only items: get_due_items'), so an agent can distinguish it without opening any schema.

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

Usage Guidelines4/5

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

Explicitly routes the deadline-only case to get_due_items and explains when to set include_hidden=true. It doesn't address how it relates to other near-neighbors (get_done_items, get_tracked_item, get_today_time_blocks), but the primary ambiguity is resolved.

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