Skip to main content
Glama
Sign In
tick-mcp

tick-mcp

by KpihX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_deleted_tasks

Retrieve deleted tasks from the trash with pagination support. Use to restore or view tasks that were previously deleted.

Instructions

Get deleted tasks from the trash.

[Category: Completed & Trash]  [Auth: V2]
[Related: delete_task, get_completed_tasks]

Args:
    start: Pagination offset (default 0).
    limit: Max results (default 50).

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

Input Schema

NameRequiredDescriptionDefault
startNo
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior2/5

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

No annotations are provided, so the description bears the full burden. It only mentions pagination parameters but omits behavioral traits like read-only nature, authentication requirements, or side effects. The minimal description does not compensate for missing annotations.

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?

The description is concise with a clear purpose line, category/related tags, and an Args section. While brief, every element serves a purpose. The structure is front-loaded and scannable.

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?

Given the tool's simplicity (2 optional params, output schema exists), the description covers the core purpose and parameter usage. It lacks details like output format or limitations, but output schema mitigates this. Overall adequate for a straightforward read tool.

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?

With 0% schema description coverage, the description adds meaning by explaining 'start: Pagination offset (default 0)' and 'limit: Max results (default 50)', clarifying their role in pagination beyond schema defaults.

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 'Get deleted tasks from the trash,' specifying the verb and resource. It distinguishes from sibling tools like get_completed_tasks and get_all_tasks by targeting deleted tasks specifically.

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?

The description includes category '[Category: Completed & Trash]' and related tools '[Related: delete_task, get_completed_tasks]', hinting at usage context and alternatives. However, it lacks explicit when-to-use or when-not-to-use guidance.

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