Skip to main content
Glama

get_tasks_due_today

Retrieve all tasks due today from Dida365 to help users manage deadlines and prioritize daily work effectively.

Instructions

获取今天到期的所有任务。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The implementation of `get_tasks_due_today` which filters tasks by checking the 'dueDate' attribute against today's date.
    def get_tasks_due_today(self) -> List[Dict]:
        """获取今天到期的任务"""
        today = datetime.now(timezone.utc).strftime("%Y-%m-%d")
        all_tasks = self.get_all_tasks()
        return [
            task
            for task in all_tasks
            if task.get("dueDate", "").startswith(today)
        ]
  • Registration of the 'get_tasks_due_today' tool in the TOOLS list.
        "name": "get_tasks_due_today",
        "description": "获取今天到期的所有任务。",
        "inputSchema": {
            "type": "object",
            "properties": {},
            "required": [],
        },
    },
  • Tool dispatch logic for 'get_tasks_due_today' in server.py, which calls the client implementation.
    elif name == "get_tasks_due_today":
        tasks = client.get_tasks_due_today()
        if not tasks:
            return "🎉 今天没有到期的任务!"
        lines = ["📅 今天到期的任务(%d 个):\n" % len(tasks)]
        for task in tasks:
            lines.append(format_task(task))
            lines.append("")
        return "\n".join(lines)
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states what the tool does ('获取今天到期的所有任务') without mentioning any behavioral traits like whether it's read-only, requires authentication, has rate limits, or what the return format might be. This leaves significant gaps for a tool that likely queries data.

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 in Chinese that directly states the tool's purpose without any unnecessary words or fluff. It is front-loaded and wastes no space, making it highly concise and well-structured.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., list format, fields included) or any behavioral aspects like error handling. For a query tool with siblings, more context is needed to guide the agent effectively.

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 any parameter information, which is appropriate here since there are no parameters to explain. This meets the baseline for tools with no parameters.

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 action ('获取' meaning 'get' or 'retrieve') and resource ('今天到期的所有任务' meaning 'all tasks due today'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from siblings like 'get_all_tasks' or 'get_overdue_tasks', 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 such as 'get_all_tasks' or 'get_overdue_tasks'. It lacks any context about prerequisites, exclusions, or comparisons, leaving the agent to infer usage based on the name alone.

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