Skip to main content
Glama
Sign In
Word AI

Word AI

by flyfish-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

docx_extract_comments

Extract comments and their full metadata from Word DOCX files for review or analysis.

Instructions

Read-only. Extract full comment metadata and text.

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": {
      "docx_path": "<docx_path>"
    },
    "name": "docx_extract_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
docx_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.6

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description bears full burden for behavioral disclosure. It only states 'Read-only', which is minimal. It does not describe what 'full metadata' entails, return format, error conditions, or performance implications.

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?

The description is exceptionally concise with two short phrases, but it sacrifices informational completeness. It earns a high score for brevity but not for substance.

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 a single parameter, no output schema, and no annotations, the description should compensate with richer details. It does not describe return values, data structure, or potential errors, making it insufficiently complete.

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?

Schema coverage is 0% and the description does not elaborate on the sole parameter 'docx_path'. It fails to clarify that this is the path to the .docx file, leaving the agent to infer from 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 verb 'Extract' and the resource 'full comment metadata and text', indicating read-only operation. While it does not explicitly differentiate from the sibling 'docx_list_comments', the use of 'extract' versus 'list' implies more comprehensive retrieval.

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 indicates the tool is read-only, advising safe usage without modifications. However, it provides no explicit guidance on when to use this tool versus siblings like 'docx_list_comments' or other extraction tools.

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