Skip to main content
Glama

Coline

List my tasks

list_my_tasks
Read-onlyIdempotent

Lists the person's own tasks across every board in the workspace.

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": {
      "workspace": "<workspace>"
    },
    "name": "list_my_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNodue_date
limitNo
filterNoopen
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
tasksYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.9/5.0
Behavior3/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 contributes the useful detail that results span every board and are scoped to the calling person, but it is silent on behavior the annotations do not cover — notably that the default filter returns only open tasks and that results are capped at 20 by default.

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?

A single front-loaded sentence with no filler or redundancy. It is tight, though the brevity is partly achieved by omitting content rather than by disciplined editing.

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

Completeness2/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 explained, and annotations cover the safety profile. However, for a 4-parameter tool with 25% schema coverage and a non-obvious default filter of 'open', the description should disclose default scoping and pagination behavior; it does neither, leaving the agent likely to misreport completeness of results.

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 only 25% — only 'workspace' is documented — so the description carries the burden of explaining sort, limit, and filter. It adds nothing: it does not clarify that 'filter' defaults to 'open' (excluding completed tasks), what 'limit' caps, or how sorting applies across boards. The enum values are self-explanatory but the defaults and their effects go unexplained.

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 ('Lists') and resource ('the person's own tasks'), and adds a scope qualifier ('across every board in the workspace') that separates it from a board-scoped task lister. It never names a sibling such as list_tasks, filter_tasks, or search_tasks, so the differentiation stays implicit rather than explicit.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no mention of alternatives, despite siblings like list_tasks, filter_tasks, search_tasks, and list_deleted_tasks that an agent must choose among. 'Own tasks' hints at a personal-scope use case, but the agent is left to infer when this tool beats a filtered or searched listing.

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