Skip to main content
Glama
Sign In
Office Word MCP Server

Office Word MCP Server

by GongRzhe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

customize_footnote_style

Modify footnote numbering format, starting number, and font style in Microsoft Word documents to meet specific formatting requirements.

Instructions

Customize footnote numbering and formatting in a Word document.

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": {
      "filename": "<filename>"
    },
    "name": "customize_footnote_style"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYes
numbering_formatNo1, 2, 3
start_numberNo
font_nameNo
font_sizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.0.0
    • removedInput schema / properties / filename / title
      Removed value: -"Filename"
    • removedInput schema / properties / font_name / title
      Removed value: -"Font Name"
    • removedInput schema / properties / font_size / title
      Removed value: -"Font Size"
    • removedInput schema / properties / numbering_format / title
      Removed value: -"Numbering Format"
    • removedInput schema / properties / start_number / title
      Removed value: -"Start Number"
  2. First observed

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'customize' which implies mutation, but doesn't disclose critical behavioral traits like whether changes are destructive to existing footnotes, permission requirements, error conditions, or what happens when applied to documents without footnotes. This leaves significant gaps for a mutation 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?

The description is a single, efficient sentence that states the core purpose without unnecessary words. It's appropriately sized and front-loaded with the essential information, making every word earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with 5 parameters, 0% schema coverage, no annotations, and no output schema, the description is inadequate. It doesn't explain what the tool returns, error conditions, side effects, or how it interacts with existing document structure. Given the complexity and lack of structured documentation, the description should provide much more context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage for all 5 parameters, the description doesn't compensate at all. It mentions 'numbering and formatting' which hints at some parameters, but provides no specifics about what 'numbering_format' accepts, what 'font_name' values are valid, or how 'start_number' interacts with existing footnotes. The description adds minimal value beyond the parameter names themselves.

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?

The description clearly states the action ('customize') and target ('footnote numbering and formatting in a Word document'), providing a specific verb+resource combination. However, it doesn't explicitly distinguish this tool from sibling footnote-related tools like 'add_footnote_enhanced' or 'validate_document_footnotes', which would be needed for a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With multiple sibling tools related to footnotes (e.g., add_footnote_enhanced, delete_footnote_from_document, validate_document_footnotes), there's no indication of whether this tool is for initial setup, modification, or other specific contexts.

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

Deploy Server

Other Tools