Skip to main content
Glama

Rewrite a draft section (server pipeline)

flypost_rewrite_section

Rewrite one highlighted passage of a post draft per an instruction, optionally with web research. Blocks until the rewritten text is ready (~1-3 minutes).

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": {
      "draft_id": "<draft_id>",
      "section_text": "<section_text>",
      "instruction": "<instruction>"
    },
    "name": "flypost_rewrite_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
draft_idYes
instructionYesHow to change it.
section_textYesThe exact passage from the draft to rewrite.
use_researchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare a non-read-only, open-world, non-destructive operation; the description adds genuinely new operational context by disclosing that the call blocks until completion and takes roughly 1-3 minutes, which materially affects how an agent should plan. It stops short of saying whether the rewritten text is written back into the draft or only returned, which matters for a mutating 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?

Two tight sentences with the core action first and the latency warning second; nothing is redundant and no sentence is filler.

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?

With no output schema, the description should carry the return-value burden; 'blocks until the rewritten text is ready' implies text comes back but does not confirm persistence into the draft or whether the highlighted passage is replaced in place. For a four-parameter mutating pipeline call with no output schema, that leaves a meaningful gap.

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 50%: instruction and section_text are documented in the schema, but draft_id and use_research are bare. The description compensates for use_research ('optionally with web research') and partially for section_text ('one highlighted passage'), leaving draft_id relying on its self-explanatory name. That lands at the baseline-plus level rather than adding rich per-parameter detail.

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 (rewrite), a precise resource (one highlighted passage of a post draft), and the driving input (an instruction). The scope word 'one' and 'passage' make it distinguishable from a whole-article rewrite, though the sibling flypost_rewrite_article_section is never named, so the agent must infer the split itself.

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?

Usage is only implied: the description makes clear this is for surgically fixing a single passage rather than regenerating a draft, and it hints that web research is an opt-in variant. It never says when to prefer this over flypost_rewrite_article_section, nor does it state prerequisites such as the draft needing to exist or the passage needing to be copied verbatim from it.

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.