Skip to main content
Glama

add_footnote_to_document

Insert footnotes into specified paragraphs of a Word document. Provide filename, paragraph index, and footnote text to enhance document context and referencing.

Instructions

Add a footnote to a specific paragraph in a Word document.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameYes
footnote_textYes
paragraph_indexYes

Implementation Reference

  • Core handler function that implements the logic for adding a footnote to a specified paragraph in a Word document. Includes input validation, document loading, attempted native footnote addition with fallback to manual superscript and footnote section creation, and error handling.
    async def add_footnote_to_document(filename: str, paragraph_index: int, footnote_text: str) -> str:
        """Add a footnote to a specific paragraph in a Word document.
        
        Args:
            filename: Path to the Word document
            paragraph_index: Index of the paragraph to add footnote to (0-based)
            footnote_text: Text content of the footnote
        """
        filename = ensure_docx_extension(filename)
        
        # Ensure paragraph_index is an integer
        try:
            paragraph_index = int(paragraph_index)
        except (ValueError, TypeError):
            return "Invalid parameter: paragraph_index must be an integer"
        
        if not os.path.exists(filename):
            return f"Document {filename} does not exist"
        
        # Check if file is writeable
        is_writeable, error_message = check_file_writeable(filename)
        if not is_writeable:
            return f"Cannot modify document: {error_message}. Consider creating a copy first."
        
        try:
            doc = Document(filename)
            
            # Validate paragraph index
            if paragraph_index < 0 or paragraph_index >= len(doc.paragraphs):
                return f"Invalid paragraph index. Document has {len(doc.paragraphs)} paragraphs (0-{len(doc.paragraphs)-1})."
            
            paragraph = doc.paragraphs[paragraph_index]
            
            # In python-docx, we'd use paragraph.add_footnote(), but we'll use a more robust approach
            try:
                footnote = paragraph.add_run()
                footnote.text = ""
                
                # Create the footnote reference
                reference = footnote.add_footnote(footnote_text)
                
                doc.save(filename)
                return f"Footnote added to paragraph {paragraph_index} in {filename}"
            except AttributeError:
                # Fall back to a simpler approach if direct footnote addition fails
                last_run = paragraph.add_run()
                last_run.text = "¹"  # Unicode superscript 1
                last_run.font.superscript = True
                
                # Add a footnote section at the end if it doesn't exist
                found_footnote_section = False
                for p in doc.paragraphs:
                    if p.text.startswith("Footnotes:"):
                        found_footnote_section = True
                        break
                
                if not found_footnote_section:
                    doc.add_paragraph("\n").add_run()
                    doc.add_paragraph("Footnotes:").bold = True
                
                # Add footnote text
                footnote_para = doc.add_paragraph("¹ " + footnote_text)
                footnote_para.style = "Footnote Text" if "Footnote Text" in doc.styles else "Normal"
                
                doc.save(filename)
                return f"Footnote added to paragraph {paragraph_index} in {filename} (simplified approach)"
        except Exception as e:
            return f"Failed to add footnote: {str(e)}"
  • Tool registration using FastMCP's @mcp.tool() decorator. Defines the tool interface with type annotations and docstring (used for JSON schema generation), and delegates execution to the core implementation in footnote_tools.py.
    @mcp.tool()
    async def add_footnote_to_document(filename: str, paragraph_index: int, footnote_text: str):
        """Add a footnote to a specific paragraph in a Word document."""
        return await footnote_tools.add_footnote_to_document(filename, paragraph_index, footnote_text)
  • The function signature and docstring in the registration provide the input schema (parameters: filename:str, paragraph_index:int, footnote_text:str) and description for the MCP tool.
    async def add_footnote_to_document(filename: str, paragraph_index: int, footnote_text: str):
        """Add a footnote to a specific paragraph in a Word document."""
        return await footnote_tools.add_footnote_to_document(filename, paragraph_index, footnote_text)
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool performs a write operation ('Add'), but does not disclose behavioral traits such as permission requirements, whether the operation is reversible, error handling (e.g., invalid paragraph index), or side effects (e.g., document modification). 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 directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, with zero wasted information.

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?

Given the tool's complexity (a mutation operation with 3 parameters), lack of annotations, and no output schema, the description is incomplete. It does not cover behavioral aspects, error conditions, or return values, leaving the agent with insufficient context to use the tool effectively.

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 compensate. It implies parameters for filename, footnote text, and paragraph index, but does not add meaning beyond what the schema titles suggest (e.g., no details on filename format, paragraph index starting point, or footnote text constraints). The baseline is 3 due to adequate but minimal parameter context.

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 ('Add a footnote') and target resource ('to a specific paragraph in a Word document'), which is specific and unambiguous. However, it does not explicitly differentiate from sibling tools like 'add_endnote_to_document' or 'customize_footnote_style', 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. It does not mention prerequisites (e.g., document must exist), exclusions (e.g., cannot add footnotes to tables), or comparisons with siblings like 'add_endnote_to_document' or 'customize_footnote_style'.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/franlealp1/mcp-word'

If you have feedback or need assistance with the MCP directory API, please join our Discord server