Skip to main content
Glama
rtdesignstudio

cemainou

by rtdesignstudio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

List Tasks Tool

list_tasks
Read-only

List your team’s tasks, including yours, free tasks anyone can take, or all open items, and filter by keywords, person, project, repo, due date, or recently done to see workload or pick-up options.

Instructions

Tasks on the team's projects: yours (default), the free ones anyone can take, or all open ones; find them by words (query), a colleague's (person) or the late ones (late). Use it to show the person what is on their plate or what they could pick up. Notes come only with the person's own tasks; a free task's note arrives once they take it.

Input Schema

NameRequiredDescriptionDefault
lateNoOnly tasks past their due date.
repoNoThe git remote of the working directory, to keep only that project's tasks.
queryNoWords to find in the title or details (searches all open tasks unless scope says otherwise).
scopeNomine = assigned to the person (default), free = nobody's yet, all = every open task, ideas = ideas noted for later.
personNoA colleague's name or email: the tasks assigned to them.
projectNoProject slug or name, when there is no repo.
sessionNoThis session's id, from the cemainou line at the start of the session. The session's project wins over the repo.
include_doneNoAlso tasks finished in the last 7 days.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

The readOnly annotation covers the safety profile, and the description adds meaningful behavioral detail about note visibility: notes come only with the person's own tasks, and a free task's note appears only after it is taken. It does not describe result limits, ordering, or pagination.

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?

The description is compact and front-loads scope options and filters before stating usage and note-access caveats. The sentences are dense but each carries relevant information.

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 read-only task listing tool with a fully documented schema and no output schema, the description covers the main use cases and the important note-visibility behavior. It leaves lower-level details like include_done, ideas scope, and repo/project/session precedence to the schema.

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 description coverage is 100%, so the schema already documents all eight parameters. The description restates a few key filters and the default scope but adds little parameter semantics beyond what the schema provides.

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 clearly states that this tool lists tasks on team projects and specifies the default scope (mine), free tasks, and all open tasks. It does not explicitly name sibling tools like my_day or search, so the distinction relies on the reader inferring scope differences.

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 provides clear usage context: use it to show what is on a person's plate or what they could pick up. It does not state when not to use it or point to alternatives such as my_day or search.

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

Deploy Server

Other Tools