Treehole MCP Server

rest

Pause AI execution for a specified duration to manage task timing. Define a reason and duration for the break.

Instructions

休息一下 - 让AI休息指定的时间，可用于延时和定时执行

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": {
      "reason": "<reason>",
      "duration": "<duration>"
    },
    "name": "rest"
  }
}

Input Schema

Name	Required	Description	Default
`reason`	Yes	休息的理由
`duration`	Yes	休息时长（秒）

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0May 14, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the effect (AI rests for a specified time) but does not mention behavioral traits like whether the rest can be interrupted, side effects, or authentication needs. Minimal but adequate for a simple tool.

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 sentence that is concise and front-loaded, with no wasted words. It effectively communicates the tool's purpose and use case.

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 simplicity of the tool (2 parameters, no output schema, no nested objects), the description is sufficiently complete. It covers purpose and usage, though it could mention that the AI will pause execution or that duration has a maximum.

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?

Schema coverage is 100%, so the input schema already describes the parameters. The description mentions 'reason' and 'duration' but adds no additional meaning beyond what the schema provides. Baseline score of 3 is appropriate.

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 action ('rest') and the resource ('AI'), and mentions its use cases ('延时和定时执行'), but does not explicitly differentiate from sibling 'vent', which may have a similar purpose.

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 provides implied usage context ('可用于延时和定时执行') but lacks explicit guidance on when not to use it or alternatives (e.g., sibling 'vent'). No exclusions or prerequisites are mentioned.

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

restA
ventC