Skip to main content
Glama

保存未发送草稿

app_save_draft

Persists input-box drafts and target paths to the backend in real time, preventing lost text when the side panel collapses.

Instructions

UI 专用:实时把输入框草稿与目标路径持久化到后端,防收起面板丢失。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "app_save_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNo
textNo
sourceDirNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose real-time persistence to the backend and the failure mode it prevents (draft loss on panel collapse). It omits whether saves are idempotent, whether writes overwrite per key, and what is returned, which matters for a mutation tool with zero annotation coverage.

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?

One sentence, front-loaded with the 'UI 专用' constraint, and every clause adds information: what is persisted, when, and why. No filler.

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?

For a three-parameter write tool with no annotations, no parameter descriptions, and no output schema, the definition says nothing about key semantics, return behavior, or write scope. Adequate on intent but not complete enough for reliable invocation.

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 coverage is 0% and three parameters are undocumented. The phrase '输入框草稿与目标路径' loosely hints that text is the draft and sourceDir is the target path, but the key parameter (the persistence slot/identity) gets no explanation, so the description compensates only partially.

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 uses a specific verb (persist, 持久化) and resource (input-box draft plus target path) and scopes it with 'UI 专用', which separates it from state/session siblings like app_get_state. It stops short of explicitly naming a contrasting sibling, so it is clear but not fully differentiated.

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?

'UI 专用' plus '防收起面板丢失' implies the usage context: it is called only by the UI, and only on draft changes where panel collapse could lose input. No explicit when-not or alternative tool is given, so guidance is implied rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.