Skip to main content
Glama
Martinqi826

Dida365 MCP Server

by Martinqi826
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_overdue_tasks

Retrieve all overdue tasks from Dida365 to identify and address pending items requiring immediate attention.

Instructions

获取所有已过期（逾期）的任务。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/dida_mcp/client.py:251-265 (handler)
    The get_overdue_tasks method in DidaClient fetches all tasks and filters them to identify those that are overdue based on their due date and completion status.
    def get_overdue_tasks(self) -> List[Dict]:
    """获取已过期的任务"""
    now = datetime.now(timezone.utc)
    all_tasks = self.get_all_tasks()
    overdue: List[Dict] = []
    for task in all_tasks:
        due = task.get("dueDate")
        if due and task.get("status", 0) == 0:
            try:
                due_dt = datetime.fromisoformat(due.replace("Z", "+00:00"))
                if due_dt < now:
                    overdue.append(task)
            except ValueError:
                continue
    return overdue

Tool Definition Quality

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states what the tool does ('get all overdue tasks') without adding context such as whether it's a read-only operation, if it requires authentication, how results are formatted, or any rate limits. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 a single, efficient sentence: '获取所有已过期（逾期）的任务.' It is front-loaded with the core purpose and contains no unnecessary words or redundancy, making it highly concise and well-structured for quick comprehension.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity is low (0 parameters, no output schema), the description is minimally adequate. It states the purpose clearly but lacks behavioral context (e.g., read/write nature, response format) and usage guidelines. Without annotations or an output schema, the description should do more to compensate, but it meets the basic requirement for a simple retrieval 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?

The input schema has 0 parameters with 100% coverage, meaning no parameters are documented in the schema. The description doesn't add parameter details, but since there are no parameters, this is acceptable. The baseline for 0 parameters is 4, as the description doesn't need to compensate for missing param info, but it also doesn't enhance understanding beyond the 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 clearly states the tool's purpose: '获取所有已过期（逾期）的任务' translates to 'Get all overdue tasks.' It specifies the verb ('get') and resource ('overdue tasks'), making the function unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_all_tasks' or 'get_tasks_due_today,' which is why it doesn't reach a score of 5.

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 description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'get_all_tasks' (which might include overdue tasks) or 'get_tasks_due_today' (which focuses on a specific due date), leaving the agent to infer usage based on context alone. This lack of explicit comparison or exclusion criteria limits its helpfulness.

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/Martinqi826/dida-mcp'

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