Skip to main content
Glama
Sign In
dayuan-lite

dayuan-lite

by lighters
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

dayuan_read_start

Idempotent

Submit a read-only query task to a remote WeCom data service and optionally wait for its result using a stable request ID. Use it to search groups, read chats, or search messages.

Instructions

提交只读查询任务给远端大渊。远端仍有自身能力；本客户端只暴露查询模板，不能保证服务器强制只读。request_id 必须稳定，超时不得换号重发；同一 ID 重复调用只恢复原任务。wait_seconds 可让服务端等待结果。

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": {
      "request_id": "<request_id>",
      "operation": "<operation>"
    },
    "name": "dayuan_read_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatNo
limitNo
queryNo
sinceNo
untilNo
operationYes
request_idYes
wait_secondsNo服务端在本次调用内按同一 request_id 轮询结果的最长秒数（0–30）；到时仍未完成则返回当前状态。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Adds real context beyond annotations: warns that despite the read-only query template the server may not enforce read-only (consistent with readOnlyHint=false), and that request_id must be stable with no retry-on-timeout under a new ID, since a repeat call only resumes the original task. This matches idempotentHint=true and tells the agent exactly what failure looks like. Missing permission/auth notes keeps it from a 5.

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?

Four tight sentences, front-loaded with the purpose and then the critical caveats (non-enforced read-only, request_id stability). No filler, though the density of caveats makes it slightly cryptic on first read.

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?

For an 8-parameter async submit tool with no output schema, the async lifecycle is covered but the operation enum values and date/filter parameters are not, and there is no hint of what the submission returns (task id/status). Adequate but with clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 13% across 8 parameters, so the description must carry the burden. It explains request_id and wait_seconds well, but leaves operation (the enum driving the three query modes), query, chat, limit, since, and until entirely undocumented in prose.

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?

States a specific verb and resource: submit a read-only query task to the remote Dayuan service. The distinction from dayuan_read_result (fetch results) and dayuan_status is implicit but reasonably clear from '提交…任务'. It lacks an explicit sibling comparison, so not a 5.

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 explains the polling contract (wait_seconds) and re-invocation semantics, which implies this is the submit step. But it never names dayuan_read_result as the follow-up tool or states when NOT to use this tool, leaving the workflow routing to inference.

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