Skip to main content
Glama
Sign In
grp-docx-mcp

grp-docx-mcp

by Arvindh95Censof
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_equation

Insert a LaTeX equation as OMML into a Word document after a specified paragraph. Provide the LaTeX source and the target paragraph ID.

Instructions

Insert a LaTeX equation as OMML. Requires: pip install latex2mathml.

Args: para_id: paraId of the paragraph after which the equation is inserted. latex: LaTeX source string (e.g. r"\frac{1}{2}").

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": {
      "para_id": "<para_id>",
      "latex": "<latex>"
    },
    "name": "add_equation"
  }
}

Input Schema

NameRequiredDescriptionDefault
latexYes
para_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.4

TDQS

A4.3/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose behavioral traits. It states it inserts an equation, implying mutation, and requires a Python package. It does not mention any constraints like requiring the document to be open, but the verb 'insert' is clear enough.

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 brief and front-loaded with the core purpose. Every sentence is necessary, and the args are listed clearly without redundancy.

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?

The tool is simple, and the description covers its purpose, parameters, and a key prerequisite. An output schema exists, so return values need no explanation. Minor gaps like mentioning that the document must be open are not critical.

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

Parameters5/5

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

With 0% schema description coverage, the parameter descriptions add valuable meaning: para_id is the paragraph after which to insert, and latex is a LaTeX source with an example. This compensates fully for the lack of schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it inserts a LaTeX equation as OMML, with a specific verb and resource. Among siblings, no other tool inserts equations, so it is well-distinguished.

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

Usage Guidelines4/5

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

The description mentions a prerequisite (pip install latex2mathml), which is crucial for usage. However, it does not explicitly state when to use this tool over alternatives, though no direct alternative exists.

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