Skip to main content
Glama

List tasks for a day

list_tasks
Read-onlyIdempotent

List the tasks on one day, in the order the user sees them. Use for questions like "what's on today?" or before changing a specific day.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dayKey": "<dayKey>"
    },
    "name": "list_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayKeyYesCalendar day "YYYY-MM-DD" in the user's time zone, or "today" / "tomorrow".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context by stating results come back 'in the order the user sees them,' which matters for interpreting output, though it says nothing about empty days or result size.

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 short sentences, front-loaded with the operation and its ordering guarantee, followed by the usage cue. No filler or redundant restatement of the title.

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?

For a single-parameter, read-only list tool with rich annotations and full schema coverage, the description covers purpose, ordering and intended use. The absence of an output schema leaves the task fields unmentioned, a minor gap rather than a blocker.

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 coverage is 100% and the dayKey property already documents the 'YYYY-MM-DD' format plus the 'today'/'tomorrow' shortcuts and the user time-zone assumption. The description adds only the notion of a single day and no additional parameter meaning, so the baseline 3 applies.

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?

The description names a specific verb and resource ('List the tasks') and narrows the scope to a single day, which separates it from broader siblings like list_backlog or search_tasks. It stops short of naming an explicit alternative, so sibling differentiation is implied by the 'one day' scoping rather than stated.

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?

It gives concrete usage cues: answering 'what's on today?' and being called before modifying a specific day, which effectively tells the agent to read before mutating. No explicit when-not-to-use or named alternatives are provided, so it falls short of a 5.

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