Amazing Marvin MCP

by qemqemqem

Overview Schema Source Related Servers Discussions Admin

Python

Local

get_due_items

Retrieve overdue and due tasks to focus on urgent items. Ideal for prioritizing past-due tasks without distraction.

Instructions

Get overdue and due tasks only (past due date).

Use when you need to focus specifically on urgent/overdue items. For complete daily view including today's tasks, use get_daily_productivity_overview().

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_due_items"
  }
}

Input Schema

Name	Required	Description	Default
`debug`	No

Output Schema

Name	Required	Description	Default
`data`	Yes
`metadata`	Yes	Metadata about the data itself
`summary`	Yes	Human-readable insights
`debug`	Yes
`success`	Yes
`api_version`	No		current
`response_version`	No		1.0

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Jun 10, 2026

TDQS

A4.1/5.0

Behavior3/5

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

No annotations provided, so description carries full burden for behavioral disclosure. It indicates a read operation by getting tasks but does not disclose auth needs, scope (e.g., user-specific or project-wide), pagination, or side effects. Lacks deeper behavioral context beyond filtering, but the core behavior is clear.

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 two sentences plus a usage line, all front-loaded and essential. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Has an output schema (not shown) and a single optional parameter. The description explains the filtering logic but omits scope details (e.g., whether tasks are user-specific or from all projects). Given sibling tools like get_all_tasks, clarifying scope would improve completeness, but overall adequate for a simple tool.

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

Parameters2/5

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

The input schema has one parameter (debug boolean with default false) at 0% schema description coverage. The tool description does not mention the debug parameter or explain its effect, so it adds no semantic value beyond the schema. A simple parameter, but the description should at least hint at its purpose.

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 clearly states 'Get overdue and due tasks only (past due date)', providing a specific verb and resource. It distinguishes from the sibling tool get_daily_productivity_overview by noting that the latter is for a complete daily view.

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 ('when you need to focus specifically on urgent/overdue items') and when not to ('For complete daily view including today's tasks, use get_daily_productivity_overview()'). Provides clear alternative.

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