Skip to main content
Glama

面灵AI 面试助手

rewrite_prompt

Read-only

提示词工作台 AI 改写:mode=refine 按 instruction 修改 draft;mode=sync 把官方后来新增的规则并入 draft,保留用户自己的改动。只返回改写后的全文与改动说明,不保存;确认后用 save_custom_prompt 保存(sync 之后保存时 baseline 传 official)。有频次限制。(需要用户授权,范围 interviews:write)

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": {
      "scene": "<scene>",
      "mode": "<mode>",
      "draft": "<draft>"
    },
    "name": "rewrite_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo
modeYes
draftYes
sceneYes
instructionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with that, adding that nothing is persisted and only the rewritten text plus a change note is returned. It also discloses a rate limit and the required authorization scope (interviews:write), which are genuinely useful beyond the annotations. It stops short of saying what the change note looks like or how throttling manifests.

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?

The tool identity and mode split are front-loaded, and every clause carries operational information (modes, non-persistence, save handoff, rate limit, auth scope). It is one dense run-on sentence with parentheticals, which slightly hurts scanability, but there is no filler.

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 non-persisting rewrite tool with no output schema, the description covers the full lifecycle: rewrite, return, confirm, save, and the auth/rate constraints. The remaining gap is that the required scene parameter and lang are unexplained, which matters because scene likely selects which prompt template family is being rewritten.

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 description coverage is 0%, so the description carries the burden, and it explains mode's two values, what instruction does, and that draft is the input being rewritten. However, the required scene parameter (interview | exam) and lang are never mentioned, leaving the meaning of two of five parameters — including a required one — to enum values alone.

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?

The description names a specific verb and resource (AI rewrite of a prompt draft in the prompt workbench) and immediately splits the behavior into the two named modes, explaining what each does. An agent can tell this apart from save_custom_prompt, which it explicitly defers persistence to.

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

Usage Guidelines5/5

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

It states when each mode applies (refine = revise draft per instruction; sync = merge newly added official rules while preserving user edits) and names the follow-up alternative explicitly: use save_custom_prompt after confirming, passing baseline=official when the edit came from sync. That is an explicit when-to-use plus a conditional routing rule.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources