Skip to main content
Glama
Sign In
DrissionPage-MCP

DrissionPage-MCP

by hooplus1ce
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

选择日期

antd_date_pick

Pick a date in an Ant Design DatePicker by clicking the input and selecting the target day from the portal calendar. Provide the element ID and date to automate date selection.

Instructions

操作 AntD 日期选择器（DatePicker）：真实点击输入框，在 portal 日历中点击目标日期。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "element_id": "<element_id>",
      "date": "<date>"
    },
    "name": "antd_date_pick"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes目标日期，格式 YYYY-MM-DD
tab_idNo标签页 id，省略时用最新标签页
timeoutNo等待日历浮层出现的秒数
element_idYes日期输入框元素的 element_id（find_element 定位 '.ant-picker' 等）

Output Schema

NameRequiredDescriptionDefault
okYes
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

The description reveals the operational sequence: real-click the input to open the portal calendar, then click the target date. It does not mention error scenarios or side effects, but the non-read-only annotation and click description provide reasonable transparency for a simple action.

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, concise sentence that directly states the tool's function without unnecessary words or repetition. It is well-structured and easy to parse.

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?

For a simple click-based date selection tool, the description sufficiently explains the core behavior. It omits return-value details, but given the full schema coverage and low complexity, the overall context is adequately complete.

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?

The parameter descriptions in the schema are complete (100% coverage) with clear details for date format, timeout, and how to obtain element_id. The main description adds no extra parameter information, so the baseline score of 3 is appropriate.

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?

Description clearly states the action: it operates an AntD DatePicker by clicking the input to open the calendar and then clicking the target date. This makes the tool's purpose unambiguous and distinguishes it from other AntD interaction tools.

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

Usage Guidelines3/5

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

The description identifies the target component (AntD DatePicker) but does not explicitly compare with sibling tools or state when to choose this tool over alternatives. The use case is implied rather than explicitly guided.

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