Skip to main content
Glama

Get tasks for a day

get_tasks
Read-onlyIdempotent

Read the user's Habidu schedule for ONE day: timed tasks, all-day tasks, repeating tasks and routines that occur that day, sorted by start time, each with its id, title, time, duration, done state and steps (subTasks). Use it before update_task or delete_task to get the ids, and to answer "what is on my day". Unscheduled captures are in get_inbox, not here; the full routine list is get_routines. An empty day returns count 0. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD in the user's local calendar, e.g. "2026-11-20". Omit for their local today.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is largely covered. The description still adds real context: sort order by start time, the returned field set (id, title, time, duration, done state, steps), and the empty-day empty-result behavior (count 0). Slight deduction because there is no output schema, so richer return-shape or edge-case detail would have been worth including.

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?

Three tight sentences, front-loaded with the scope, then routing guidance, then return/edge-case behavior. No redundant or filler wording; every clause carries information the agent needs.

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 one-parameter read tool with no output schema, the description supplies what is asked for and the shape of the result, including empty-day behavior and sorting. Nothing needed to call it correctly or interpret the response is missing.

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% and the single date parameter documents YYYY-MM-DD format plus the omit-for-today default. The description only reinforces single-day scope ('ONE day', 'that day'), which is marginal added meaning, so the baseline of 3 applies.

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?

Specific verb and resource scoped to 'ONE day', enumerating what is included (timed, all-day, repeating tasks and routines) plus sort order and returned fields. It also explicitly distinguishes itself from get_inbox (unscheduled captures) and get_routines (full routine list), so an agent can route correctly without opening another schema.

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?

Gives explicit use cases ('before update_task or delete_task to get the ids', 'what is on my day') and names the alternatives with their exclusions. Both when-to-use and when-not-to-use are covered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources