Skip to main content
Glama

login

Authenticate with TickTick using OAuth credentials. A browser opens for authorization, enabling task management through the MCP server.

Instructions

Log in to TickTick by providing OAuth credentials.

Ask the user for all four parameters. They can be found on the developer console app settings page:

Args: client_id (required): OAuth application Client ID, shown on the app page. client_secret (required): OAuth application Client Secret, shown on the app page. account_type (optional, default "china"): "china" for Dida365 or "global" for TickTick international. Use the default unless the user explicitly says they use the international version (ticktick.com). redirect_uri (optional, default "http://localhost:8000/callback"): the callback URL configured in the developer console. Use the default unless the user explicitly states a different value. Never invent a URL — if the user does not provide one, use the default.

After calling this tool, a browser window opens automatically for the user to authorize. The tool blocks until authorization completes or times out (up to 120 seconds).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_idYes
account_typeNochina
redirect_uriNohttp://localhost:8000/callback
client_secretYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that a browser window opens, the tool blocks, and it can time out after 120 seconds. It also warns against inventing URLs. Minor omission: no explicit mention of what happens on success or failure beyond timeout, but the output schema exists.

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?

The description is well-structured with an opening summary, helpful URLs, a clear Args list, and a behavioral note. Every sentence contributes practical value; no filler or redundancy.

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?

The tool is an interactive OAuth flow with four parameters and no annotations. The description covers purpose, credential sourcing, parameter defaults, user prompting, browser behavior, and timeout handling. Combined with the output schema, this is complete for an agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description fully compensates: it explains each parameter's meaning, required status, default values, where to find them, and even provides conditional usage guidance (e.g., 'Use the default unless the user explicitly says...'). This is exemplary parameter documentation.

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?

The description opens with a specific verb+resource: 'Log in to TickTick by providing OAuth credentials.' This clearly distinguishes login from the operational sibling tools (project/task/habit management) and states the exact purpose.

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 explicitly instructs to 'Ask the user for all four parameters' and provides concrete decision rules for optional parameters (e.g., use default unless user explicitly states otherwise). It does not mention when not to use the tool, but login is a prerequisite for all other tools, making the usage context clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Code-MonkeyZhang/ticktick-mcp-enhanced'

If you have feedback or need assistance with the MCP directory API, please join our Discord server