Skip to main content
Glama
KpihX

tick-mcp

by KpihX
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_completed_tasks

Retrieve completed or abandoned tasks within a date range to review task history and track productivity.

Instructions

Get completed or abandoned tasks within a date range.

[Category: Completed & Trash]  [Auth: V2]
[Related: complete_task, get_deleted_tasks, get_productivity_stats]

Args:
    from_date: "yyyy-MM-dd HH:mm:ss", e.g. "2026-01-01 00:00:00".
    to_date: "yyyy-MM-dd HH:mm:ss", e.g. "2026-12-31 23:59:59".
    status: "Completed" or "Abandoned" (default: "Completed").
    limit: Max results (default 100).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
from_dateYes
to_dateYes
statusNoCompleted
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.5/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses date range, status options, limit, and auth, but does not mention ordering or pagination 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?

Front-loaded with purpose, then additional info in compact format. No wasted sentences.

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?

Output schema exists, so return values are covered. Description addresses core behavior and parameters; could mention pagination but not necessary for a simple retrieval tool.

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 has 0% description coverage; description adds format examples, defaults, and constraints for each parameter, fully compensating for the gap.

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?

Clearly states 'Get completed or abandoned tasks within a date range', specifying verb, resource, and scope. Distinguishes from siblings via 'Related' section.

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?

Provides context via 'Related' list indicating alternatives, but does not explicitly state when not to use this tool. The category and auth info add guidance.

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/KpihX/tick-mcp'

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