Skip to main content
Glama

get_my_tasks

Read-onlyIdempotent

Retrieve your assigned tasks non-blockingly and filter them by status category to focus on active work, with compact results by default.

Instructions

Get YOUR assigned tasks, non-blocking. Use list_tasks to browse or search other people's tasks in a project, poll_tasks only to block until a new assignment arrives. Filterable by status_category to focus on active work. Default (cold) view is compact: only in_progress, review and the top 5 todo are requested and listed (envelope omitted counts the todo past the cap, has_more flags open cards past limit; done, cancelled and backlog need full=true or status_category), descriptions are omitted (has_description marks them; get_task(id) or full=true returns the full text). Envelope fields (created_by/created_at, assignee_id) and valueless fields (0-counters, due_date=null, human_gate=false) are omitted; full=true returns the complete items and get_task returns one card's full details.

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

Input Schema

NameRequiredDescriptionDefault
fullNoReturn complete non-capability REST fields; always bypasses revision and delta shortcuts.
limitNoMax results (default 50).
project_idNoFilter by project.
accept_deltaNoOpt in to lossless delta against known_revision: complete changed items, removed_ids, full order and non-items envelope. Apply only to the retained matching base; otherwise omit known_revision and retry cold.
known_revisionNoRevision of a complete snapshot retained for this session and the same filters/view. Omit after cache loss, restart or compaction to request complete cold. Exact match returns unchanged=true; mismatch returns complete cold unless accept_delta=true.
status_categoryNoFilter by status category: backlog, todo, in_progress, review, done, cancelled.
snapshot_sessionNoOpaque non-secret consumer cache namespace. Required for conditional responses on stateless HTTP. Use a fresh value after restart or compaction; never credentials or lease tokens.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare the safe read-only/idempotent profile; the description goes far beyond by disclosing the non-blocking nature, the default compact projection (only in_progress, review, top 5 todo), that descriptions are stripped and flagged via has_description, and that envelope/valueless fields are dropped. It also explains what the envelope's omitted counts and has_more signify, which is real behavioral context an agent needs to interpret results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and sibling routing are front-loaded in the first two sentences, and every subsequent sentence carries substantive information. The dense parentheticals and semicolon-chained clauses make it harder to scan than it needs to be, but there is no filler.

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?

With 7 parameters, no output schema, and a compact-by-default response shape, the description compensates by explaining the projection rules, the omission markers, and the envelope counters an agent must interpret. Nothing essential for calling or reading the response correctly appears to be missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds behavioral meaning the schema does not: status_category is framed as focusing on active work and as a way to reach done/cancelled/backlog, full=true is described as returning complete items and full text, and the 5-item todo cap under the default view gives limit real consequence. It does not clarify the delta/revision/session parameters, which is the only remaining 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 (Get ... assigned tasks) plus the crucial scope qualifier 'YOUR' and the behavioral trait 'non-blocking'. It actively distinguishes itself from three siblings (list_tasks, poll_tasks, get_task), so an agent can select it without opening a 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?

Explicit when-to-use routing: list_tasks to browse or search other people's tasks, poll_tasks only to block until a new assignment arrives. It also gives conditional alternatives for detail retrieval ('get_task(id) or full=true') and says when status_category or full=true are needed to see done, cancelled or backlog work.

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