Skip to main content
Glama
WilliamSmithEdward

xlide-excel-word-powerpoint-access-office-vba-mcp

by WilliamSmithEdward
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Notes and comments

xlide_manage_comment
DestructiveIdempotent

List, add, reply to, resolve, or remove Excel cell comments—both notes and threaded conversations—to document or discuss worksheet data.

Instructions

Lists, writes, answers or removes the comments on a worksheet's cells. Excel has two kinds: a note, the yellow box that shows on hover, and a threaded comment, the conversation on the Review tab with replies and a resolved state. action='list' reads both and changes nothing. 'set' writes a note, replacing one already on the cell, or with kind='thread' starts a conversation; 'reply' and 'resolve' act on a thread; 'remove' takes either kind off the cell. Use a note to explain a cell to whoever reads the workbook next.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cellNoThe cell, such as B4. For list, empty lists the sheet.
kindNoFor set: 'note' or 'thread'.note
textNoFor set and reply: what the comment says.
sheetYesWorksheet name, matched without case.
actionNolist, set, reply, resolve or remove.list
authorNoWho wrote it, as the workbook shows the name.Agent
offsetNoFor list: comments to skip.
visibleNoFor a note: shown all the time, not only on hover.
resolvedNoFor resolve: false opens a thread again.
file_pathYesAbsolute path to the Excel file.
max_resultsNoFor list: most comments to return.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.2
    • addedInput schema / properties / max_results
      Added value: +{
+  "default": 300,
+  "description": "For list: most comments to return.",
+  "maximum": 300,
+  "minimum": 1,
+  "title": "Max Results",
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "For list: comments to skip.",
+  "minimum": 0,
+  "title": "Offset",
+  "type": "integer"
+}
  2. Addedv1.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, and the description usefully partitions behavior per action — 'list' changes nothing while 'set' replaces an existing note and 'remove' takes either kind off the cell. That per-action safety breakdown adds real context beyond the blanket annotation. It doesn't cover permissions, file-locking, or interaction with an open workbook, so not a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Content is front-loaded: the first sentence gives the core verb/resource, and the following sentences explain the note-vs-thread distinction and the action semantics. It is on the longer side for one sentence of value, but every clause carries distinguishing information.

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?

For an 11-parameter mutation tool with full schema coverage and an output schema, the description supplies the missing narrative: what each action does, which ones mutate, and which apply to threads only. Remaining gaps (pagination behavior, replacement/undo semantics beyond the note case) are minor.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not spell out — e.g. that 'reply' and 'resolve' only apply to threads, and that 'set' with kind='thread' starts a conversation. It stops short of explaining cell/offset/max_results semantics, which the schema already handles.

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?

States specific verbs (lists, writes, answers, removes) against a specific resource (comments on a worksheet's cells), and explicitly disambiguates the two Excel comment kinds (note vs threaded comment). An agent can identify exactly what this tool does and how it differs from all siblings, none of which touch comments.

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?

Maps each action value to its effect ('list' reads both and changes nothing, 'set' writes/replaces, 'reply'/'resolve' act on a thread, 'remove' clears either kind off the cell) and gives a usage rule: 'Use a note to explain a cell to whoever reads the workbook next.' It does not name when another sibling would be preferred, so it stops short of a 5.

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