Skip to main content
Glama

list_projects

Read-only

Retrieve TickTick projects, including Inbox, with IDs, names, colors, and permissions to select the correct projectId for task tools.

Instructions

List TickTick projects, including the Inbox alias, with their IDs, names, colors and permissions. Use the returned projectId in task tools.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered structurally. The description adds real context by naming the returned fields and flagging the Inbox alias as a special entry, but says nothing about how the listing is bounded or ordered despite having limit/offset parameters.

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?

Two short sentences, front-loaded with purpose and ending with the actionable follow-up about projectId. No filler, though the return-field list and the workflow hint could be more cleanly separated.

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 simple read-only list tool with no output schema, the description covers what the tool is, what an entry contains, and how the output feeds task tools. The one meaningful omission is pagination behavior for the limit/offset pair.

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?

Only two parameters exist, so the baseline is 4, and the schema's 0% description coverage is partly mitigated by the parameters being self-explanatory pagination fields with defaults and bounds already declared in the schema. That said, the description adds nothing about pagination or how to page through more than the default 200 projects.

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?

States a specific verb and resource ("List TickTick projects") and even enumerates what each entry carries (IDs, names, colors, permissions), plus the notable detail that the Inbox alias is included. It does not explicitly differentiate itself from the sibling get_project, which is the main thing keeping it below a 5.

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 closing sentence "Use the returned projectId in task tools" gives a useful downstream workflow hint, which implicitly frames this as a discovery/prerequisite call. However, there is no guidance on when to call this versus get_project for a single project, and no exclusions or prerequisites are stated.

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