Skip to main content
Glama

get_task

Read-only

Retrieve a single TickTick task using its project ID and task ID, including checklist items and recurrence details for inspection or updates.

Instructions

Get one TickTick task by projectId and taskId, including its checklist and recurrence.

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": {
      "projectId": "<projectId>",
      "taskId": "<taskId>"
    },
    "name": "get_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYesTickTick task ID.
projectIdYesTickTick project ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A3.7/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 safety is covered. The description adds genuinely useful return-content context ('including its checklist and recurrence'), but says nothing about behavior when the task ID is missing or the project doesn't match, and there is no output schema to fill that gap.

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?

A single front-loaded sentence with the verb and resource first and no redundant wording. Nothing could be removed without losing 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 simple two-parameter read tool with full schema coverage and read-only annotations, this is nearly sufficient; the only missing piece is a note on not-found behavior or the shape of the returned object, which no output schema supplies.

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?

Schema description coverage is 100% and both parameters are self-documented in the schema. The description still reinforces the meaning by pairing each parameter with its role (which project, which task), which is a small but real addition over the raw schema.

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 ('Get one TickTick task') and names the two identifying keys, so it is clearly distinguishable from the list/filter/search siblings by intent. It stops short of explicitly naming a sibling or contrasting behavior.

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?

Usage is only implied: 'by projectId and taskId' signals this is the right call when both identifiers are already known. There is no explicit when-to-use or when-not-to-use guidance, nor any pointer to list_tasks or search_tasks for the discovery case.

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