Skip to main content
Glama

haus

by app.onehaus
OverviewDiscussionsAdmin

list_tasks

Read-only

List tasks, filterable by assignee, due-date range and completion, with cursor pagination. Excludes completed tasks by default and sorts open urgent tasks first (within the returned page), then due date ascending (undated first).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoPage size, 1-100, default 50.
cursorNonextCursor from a previous response. Omit for the first page.
dueDateOnOrAfterNoEarliest due date, YYYY-MM-DD. Undated tasks never match.
includeCompletedNoInclude completed tasks. Defaults to false.
dueDateOnOrBeforeNoLatest due date, YYYY-MM-DD. Undated tasks never match.
assignedToMemberIdNoMember id to filter by. Omit for all assignees.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes
titleNo
messageNo
variantNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • changedInput schema / properties / assignedToMemberId / description
      Previous value: -"Filter to tasks assigned to this household member ID. Omit to include tasks for all assignees."New value: +"Member id to filter by. Omit for all assignees."
    • changedInput schema / properties / cursor / description
      Previous value: -"Opaque pagination cursor from a previous list_tasks response's nextCursor. Omit to fetch the first page."New value: +"nextCursor from a previous response. Omit for the first page."
    • addedInput schema / properties / cursor / examples
      Added value: +[
+  "eyJsYXN0IjoiMDE4ZjJjOWEifQ"
+]
    • changedInput schema / properties / dueDateOnOrAfter / description
      Previous value: -"Only include tasks with a due date on or after this date (YYYY-MM-DD). Tasks with no due date never match."New value: +"Earliest due date, YYYY-MM-DD. Undated tasks never match."
    • changedInput schema / properties / dueDateOnOrBefore / description
      Previous value: -"Only include tasks with a due date on or before this date (YYYY-MM-DD). Tasks with no due date never match."New value: +"Latest due date, YYYY-MM-DD. Undated tasks never match."
    • changedInput schema / properties / includeCompleted / description
      Previous value: -"Whether to include completed tasks in the results. Default: false"New value: +"Include completed tasks. Defaults to false."
    • addedInput schema / properties / includeCompleted / examples
      Added value: +[
+  false
+]
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of tasks to return per page. 1-100, default 50."New value: +"Page size, 1-100, default 50."
    • addedInput schema / properties / limit / examples
      Added value: +[
+  20
+]
  2. Changed10 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "assignedToMemberId": "7f3a9c2e1b4d8f6a0c5e3b7d9a1f4c6e",
+    "dueDateOnOrAfter": "2026-07-01",
+    "dueDateOnOrBefore": "2026-07-31",
+    "includeCompleted": false,
+    "limit": 20
+  }
+]
    • addedInput schema / properties / assignedToMemberId / description
      Added value: +"Filter to tasks assigned to this household member ID. Omit to include tasks for all assignees."
    • addedInput schema / properties / assignedToMemberId / examples
      Added value: +[
+  "7f3a9c2e1b4d8f6a0c5e3b7d9a1f4c6e"
+]
    • changedInput schema / properties / cursor / description
      Previous value: -"Pagination cursor"New value: +"Opaque pagination cursor from a previous list_tasks response's nextCursor. Omit to fetch the first page."
    • changedInput schema / properties / dueDateOnOrAfter / description
      Previous value: -"Tasks with due date on or after (YYYY-MM-DD)"New value: +"Only include tasks with a due date on or after this date (YYYY-MM-DD). Tasks with no due date never match."
    • addedInput schema / properties / dueDateOnOrAfter / examples
      Added value: +[
+  "2026-07-01"
+]
    • changedInput schema / properties / dueDateOnOrBefore / description
      Previous value: -"Tasks with due date on or before (YYYY-MM-DD)"New value: +"Only include tasks with a due date on or before this date (YYYY-MM-DD). Tasks with no due date never match."
    • addedInput schema / properties / dueDateOnOrBefore / examples
      Added value: +[
+  "2026-07-31"
+]
    • changedInput schema / properties / includeCompleted / description
      Previous value: -"Default: false"New value: +"Whether to include completed tasks in the results. Default: false"
    • changedInput schema / properties / limit / description
      Previous value: -"1-100, default 50"New value: +"Maximum number of tasks to return per page. 1-100, default 50."
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnlyHint/destructiveHint annotations, the description discloses key behavioral details: completed tasks are excluded by default, sorting is urgent-first then due-date ascending, and undated tasks sort first. This is exactly the kind of non-obvious behavior an agent needs to know.

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-loaded with the core action and filters, then the important default and ordering behavior. Every clause earns its place with no redundancy.

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 list tool with six fully documented parameters and an output schema, the description covers defaults, sorting, filtering, and pagination. The read-only safety profile is already declared by annotations, so nothing essential 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?

The input schema already provides 100% parameter coverage with clear descriptions for every parameter. The description adds a useful summary of the filter categories but does not significantly extend the schema's parameter-level semantics.

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 states a specific verb and resource ('List tasks') and immediately details the filtering dimensions (assignee, due-date range, completion) and pagination. It clearly distinguishes this from sibling task mutation tools like create_task, update_task, and complete_task.

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

Usage Guidelines3/5

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

The description clearly implies this is the tool for retrieving/filtering tasks, and the filtering options give context on when it applies. However, it does not explicitly state when to prefer an alternative or mention any exclusions, though no direct task-listing sibling exists.

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

All haus toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources