Skip to main content
Glama

AceRound AI Interview Copilot

rewrite_prompt

Read-only

Prompt studio AI rewrite: mode=refine edits the draft per instruction; mode=sync merges rules added to the official prompt into the draft while keeping the user’s own changes. Returns the rewritten text and a summary of changes without saving; save with save_custom_prompt (after sync, pass baseline=official). Rate-limited. (Requires the user's sign-in with scope 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.5/5.0
Behavior5/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 them by stating the result is returned 'without saving'. Beyond the annotations it discloses rate limiting, the exact return payload (rewritten text plus change summary), and the required auth scope (interviews:write), which is genuinely useful context an agent cannot get from structured fields.

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 core distinction between the two modes is front-loaded, and the parenthetical at the end efficiently bundles the no-save, auth, and rate-limit caveats. It is dense rather than padded, though the single sprawling structure with two parentheticals reads as crammed and could be split for scannability.

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?

With no output schema, the description correctly states the return value (rewritten text plus change summary), and it covers persistence, auth, and rate limits for a moderately complex five-parameter tool. The remaining gap is the unexplained 'scene' and 'lang' parameters, which an agent can only resolve by inspecting the raw enums.

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 must carry parameter meaning; it only partially does, fully explaining the two values of 'mode' by their behavior. The 'scene' enum (interview vs exam), 'lang', 'draft' and 'instruction' parameters get no elaboration at all, and 'scene' in particular changes the tool's target domain.

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 opens with a specific verb+resource ('Prompt studio AI rewrite') and immediately distinguishes the two operating modes, refine vs sync. It also names the sibling that handles persistence (save_custom_prompt), so an agent can tell exactly what this tool does and does not do.

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?

Explicit routing rules are given: mode=refine edits per instruction, mode=sync merges rules from the official prompt into the draft while preserving user edits. It states the alternative ('save with save_custom_prompt') and even the follow-up condition ('after sync, pass baseline=official'), leaving nothing to inference.

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