Skip to main content
Glama
Sign In
Office-MCP-Server

Office-MCP-Server

by stoyantsiparov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

word_highlight_text

Search a Word document for specified text and apply highlight colors to matching paragraphs. Provide search terms and colors to visually annotate key sections.

Instructions

Search for text and apply a highlight color to matching paragraphs

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": {
      "file_path": "<file_path>",
      "edits": "<edits>"
    },
    "name": "word_highlight_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
editsYesList of search terms and the highlight color to apply to each
file_pathYesAbsolute path to the .docx file
case_sensitiveNoMatch case exactly (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action without mentioning side effects (e.g., in-place document modification, overwriting existing highlights), the scope of highlighting (whole paragraph vs exact match), or return behavior. This is a significant gap 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, front-loaded sentence with no filler. Every word contributes to conveying the tool's purpose, making it highly concise and well-structured.

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 tool with no output schema and no annotations, the description is too thin. It fails to clarify whether the highlight applies to entire paragraphs or exact text matches, what happens to existing highlights, or what the tool returns after modification. The sibling context suggests related tools, but the description itself lacks essential completeness.

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 100%, so all parameters are documented in the schema. The description adds minimal semantic nuance beyond 'search' and 'color' mapping, so the baseline score of 3 applies.

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 the action (search and apply highlight) and the resource (text/paragraphs in a Word document). It distinguishes itself from siblings like word_search_text (search only) and word_format_text (general formatting) by specifying the highlighting function.

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?

The description implies a use case (highlight matching text) but provides no explicit guidance on when to use this tool versus alternatives like word_search_text or word_replace_texts. No exclusions or prerequisites are mentioned, making it minimally adequate but not instructive.

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