ticktick-mcp

create_focus

Creates a focus (pomodoro) record to log timed work sessions; available only when using API-token mode.

Instructions

Creates a focus (pomodoro) record. API-token mode only.

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": {
      "body": "<body>"
    },
    "name": "create_focus"
  }
}

Input Schema

Name	Required	Description	Default
`body`	Yes	Focus record fields

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.2.1Oct 1, 2026

TDQS

B3.2/5.0

Behavior3/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. It usefully discloses a critical auth constraint ('API-token mode only') and that the operation creates a record, but it does not describe side effects, required permissions beyond token mode, idempotency, or failure behavior.

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 two short, front-loaded sentences with no filler. The primary purpose is stated first, followed immediately by the key environment constraint.

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?

For a create tool with a freeform nested body, no annotations, and no output schema, the description is too thin. It does not tell the agent what fields to supply, what the created record includes, or how to interpret the response, leaving significant gaps for correct invocation.

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 reported at 100%, so the baseline is 3. However, the single body parameter is a freeform object with no defined properties, and the description adds no field-level guidance beyond saying it is a focus (pomodoro) record.

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 states a specific verb and resource: 'Creates a focus (pomodoro) record.' This clearly distinguishes it from the sibling list_focus tool, which lists rather than creates records. It does not explicitly name or compare against any sibling, so it falls just short of the top score.

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?

The phrase 'API-token mode only' is an important precondition, but it is not guidance on when to use this tool versus alternatives. There is no mention of when a focus record should be created, what prerequisites exist, or which related tools to consider.

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