Skip to main content
Glama
evalor
by evalor

Get Task

get_task

Retrieve complete task details: title, description, dates, priority, and sub-tasks. Verify task existence or check status before updates.

Instructions

Retrieve detailed information about a specific task (任务).

WHEN TO USE:

  • View complete task details (title/标题, description/描述, dates/日期, priority/优先级)

  • Check task status before updating or completing

  • Verify a task exists

WHEN NOT TO USE:

  • List multiple tasks → use 'list_tasks'

  • Get all tasks in a project (清单) → use 'get_project_data' or 'list_tasks'

REQUIRED: projectId (清单ID), taskId (任务ID)

RESPONSE FIELDS:

  • content: Description for TEXT tasks (no sub-tasks)

  • desc: Description for CHECKLIST tasks (with sub-tasks/子任务)

  • kind: "TEXT" or "CHECKLIST"

  • items: Sub-task list (子任务列表, CHECKLIST only)

NOTE: When creating/updating, use unified 'description' parameter which auto-maps to the correct field.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskIdYesTask ID (任务ID, required)
projectIdYesProject ID (清单ID, required)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
descNoTask description for CHECKLIST tasks
etagNo
kindNo
tagsNo
itemsNo
titleYes
statusNo
contentNoTask description for TEXT tasks
dueDateNo
isAllDayNo
priorityNo
timeZoneNo
projectIdYes
remindersNo
sortOrderNo
startDateNo
repeatFlagNo
completedTimeNo
Behavior4/5

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

Although no annotations exist, the description discloses key behavioral aspects: response fields (content, desc, kind, items). It explains the distinction between TEXT and CHECKLIST tasks and includes a note about unified description parameter mapping. Missing explicit statement of read-only nature, but overall good transparency.

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?

Well-structured with clear sections (general, WHEN TO USE, WHEN NOT TO USE, REQUIRED, RESPONSE FIELDS, NOTE). All sentences add value. Slightly verbose but organized and front-loaded.

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?

For a simple get tool, the description is very complete. It covers purpose, usage guidelines, required parameters, response fields, and special behavior (TEXT vs CHECKLIST). With output schema existing, no further detail needed.

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 100%, so baseline is 3. The description adds Chinese translations and restates required parameters, but does not add substantial new meaning beyond the schema.

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 clearly states 'Retrieve detailed information about a specific task', using a specific verb and resource. It distinguishes from siblings like list_tasks and get_project_data in the WHEN NOT TO USE section.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly provides WHEN TO USE and WHEN NOT TO USE sections, naming alternatives and giving clear context for when this tool is appropriate.

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/evalor/Dida365MCP'

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