Skip to main content
Glama

Rewrite an article passage (synchronous)

flypost_rewrite_article_section
Read-only

Rewrite one passage of an article per an instruction, optionally grounded on the Brain and/or live web research. Returns the rewritten text directly.

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": {
      "article_id": "<article_id>",
      "text": "<text>",
      "instruction": "<instruction>"
    },
    "name": "flypost_rewrite_article_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe exact passage to rewrite.
use_brainNo
article_idYes
instructionYes
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?

Goes beyond the supplied annotations by disclosing that the rewritten text is returned directly and that the call is synchronous — i.e. nothing is persisted and no polling is needed — which annotations like readOnlyHint alone do not convey. Gaps remain: 'the Brain' is never defined, and the latency/cost implications of enabling live web research are unstated.

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: the action and scope first, the return behavior second. No filler, no repetition of structured fields.

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?

Adequate for a read-only generative tool with no output schema (return shape is covered by 'returns the rewritten text directly'). However, for a 5-parameter tool at 20% schema coverage it leaves the identity of article_id and the interaction of the grounding flags unresolved.

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 only 20% (just 'text'), so the description carries a real burden. It does explain that the instruction drives a rewrite and that the two boolean flags toggle Brain vs live-web grounding, but article_id is left completely unexplained and the grounding flags' interaction (both on? either?) is not clarified.

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 and resource with a clear scope: 'Rewrite one passage of an article per an instruction'. The word 'passage' signals granularity, but the description never distinguishes this from the sibling 'flypost_rewrite_section', so an agent cannot tell which of the two to pick without guessing.

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?

Implies usage through 'optionally grounded on the Brain and/or live web research' and notes the call is synchronous, which suggests when grounding flags matter. It gives no explicit when-to-use vs when-not, no prerequisites (e.g. must the article exist), and no routing to flypost_rewrite_section or flypost_save_article.

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.