Skip to main content
Glama

list_my_tasks

Read-onlyIdempotent

Retrieve your assigned or personal tasks with overdue items listed first; use status, limit, and offset filters to narrow results.

Instructions

My tasks (assigned to me or personal), overdue first. Shortcut for list_tasks(scope="mine").

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": "list_my_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
statusNoopen

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

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, so safety is covered. The description adds a genuinely non-obvious behavioral trait the annotations cannot convey: results are ordered with overdue items first. It omits pagination behavior and the fact that only open tasks are returned by default, so it is helpful but not exhaustive.

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 with the scope and ordering front-loaded and the sibling equivalence stated immediately after. Nothing is wasted and no sentence restates the name.

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

Completeness3/5

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

An output schema exists, so return values need not be described. However, the three input parameters carry no documentation anywhere, and the meaningful default status="open" (which silently excludes closed tasks) goes unmentioned, leaving a real gap for a tool with three parameters.

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?

Schema description coverage is 0% for three parameters (limit, offset, status), and the description explains none of them. Worse, the only parameter-like reference is scope="mine" from the wrapped tool, which is not a parameter of this tool and could mislead an agent into passing it. The description does not compensate for the schema gap.

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?

States a specific verb and resource (listing my tasks), the scope that defines them (assigned to me or personal), and the ordering (overdue first). It also names the sibling it wraps, so an agent can distinguish it from list_tasks without opening either schema.

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?

"Shortcut for list_tasks(scope=\"mine\")" tells the agent exactly which alternative this replaces and implicitly that list_tasks is the tool for any other scope. It stops short of stating exclusions explicitly (e.g., use search_tasks when filtering by keyword), so it is clear context rather than full when/when-not guidance.

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