Deferno MCP Server

get_items_plan

Retrieves a daily plan combining tasks, habits, chores, and events. Accepts date and timezone parameters to generate the aggregated plan for any day.

Instructions

Daily plan across all item kinds (Task, Habit, Chore, Event).

Returns a polymorphic array — each entry has a kind discriminator. date defaults to today; tz is an optional IANA 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": "get_items_plan"
  }
}

Input Schema

Name	Required	Description	Default
`date`	No
`tz`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 11, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations, the description carries the full burden. It mentions the polymorphic return type and parameter defaults, but does not disclose any side effects, read/write nature, rate limits, or pagination behavior. The behavioral disclosure is incomplete.

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?

Two sentences front-load the purpose and then provide key details on return type and parameters. Every sentence is informative and there is no waste.

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?

Given the tool returns a daily plan across multiple item kinds with an output schema, the description covers the return structure (discriminator), parameter defaults, and timezone format. Minor gaps exist (e.g., no mention of ordering or plan scope), but it is largely complete.

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?

The input schema has 0% description coverage, but the description compensates by explaining that 'date' defaults to today and 'tz' is an optional IANA timezone. This adds essential meaning beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it retrieves a daily plan covering Tasks, Habits, Chores, Events, and mentions the polymorphic array with kind discriminator. However, it does not explicitly differentiate from the sibling tool 'get_daily_plan', which may have overlapping functionality.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like 'get_daily_plan', 'get_item', or 'search_items'. The description implies usage for daily planning but does not provide explicit context or exclusions.

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

Deploy Server