Academic Writer MCP

Appliquer une mise en forme

apply_formatting

Creates a formatted copy of an imported DOCX in the exports folder, applying margins, fonts, spacing, indents, and page numbers while leaving the original and text unchanged. Set pdf=true for PDF.

Instructions

Crée une COPIE mise en forme d'un .docx importé (marges, police, taille, interligne, retraits, numéros de page) dans le dossier exports ; l'original n'est jamais modifié. Texte inchangé. pdf=true : PDF via Word.

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": {
      "document_id": "<document_id>"
    },
    "name": "apply_formatting"
  }
}

Input Schema

Name	Required	Description	Default
`pdf`	No
`preset`	No
`document_id`	Yes

Output Schema

Name	Required	Default
`notice`	No	Copie mise en forme : l'original est inchangé. Relire la copie (tableaux, figures, listes).
`preset`	Yes
`messages`	Yes
`pdf_path`	No
`document_id`	Yes
`output_path`	Yes
`headings_kept`	Yes
`page_numbers_added`	Yes
`paragraphs_formatted`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Adds context the annotations do not: the operation writes a new copy into the exports folder, the original file is never modified, and the text itself is unchanged. This resolves the tension between readOnlyHint=false and destructiveHint=false, which the annotations alone leave ambiguous. It stops short of stating permissions or what happens on name collisions in exports.

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 compact sentences, front-loaded with the core action and safety guarantee, followed by the output-mode note. Every clause carries information; nothing is redundant.

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 an output schema present, return values need not be described, and the copy-not-modify semantics plus the PDF option make the tool callable correctly. The lingering gap is the undocumented 'preset' parameter, which an agent cannot fill in without guessing.

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 meaning. It explains pdf=true (PDF generated via Word) but leaves 'preset' completely undefined and only implies document_id refers to the imported .docx. Partial compensation only.

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: creates a formatted COPY of an imported .docx in the exports folder, listing the formatting dimensions covered (margins, font, size, line spacing, indents, page numbers). It is clearly distinguished from a check-style sibling, though no sibling is named explicitly.

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 implied by the described input (an imported .docx) and by the pdf=true shortcut, which tells the agent when to request PDF output. There is no explicit when-to-use/when-not guidance and no routing away from check_formatting or export_document.

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

Deploy Server