Skip to main content
Glama
Sign In
ticktick-mcp

ticktick-mcp

by powercess
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_preferences

Fetches TickTick user preferences, including matrix rules and Quick Add settings, via web-mode access so clients can adapt their behavior to each user's saved configuration.

Instructions

Gets user preferences (matrix rules, quick-add, etc.). Web mode only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Gets' implies a read, and 'Web mode only' is a useful environment constraint, but nothing is said about permissions, whether the call is safe/idempotent, or what the response contains. Minimal disclosure for an annotation-free tool.

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 tight sentence with the core purpose front-loaded and the mode constraint appended. No wasted words, though the parenthetical examples are slightly loose.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters, no output schema, and no annotations, the description is the only source of information, and it gives only a high-level summary. For a simple read tool this is close to adequate, but the agent cannot know the structure or scope of what 'preferences' returns.

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?

The tool takes zero parameters, so the baseline of 4 applies. The description correctly implies no arguments are needed; there is nothing further to document.

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 ('Gets user preferences') and gives examples of what is included (matrix rules, quick-add). It does not need to distinguish from siblings since no other tool reads preferences, but it also doesn't enumerate the full contents due to the vague 'etc.'

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?

'Web mode only' is a real usage constraint telling the agent when the tool is callable, which is more than most getters offer. However, there is no guidance on when to reach for this versus reading preferences through other means, and no exclusions beyond the mode restriction.

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