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

grp-docx-mcp

by Arvindh95Censof
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_document_protection

Protect a Word document by selecting an edit restriction type (tracked changes, comments, read-only, or forms) and applying an optional password.

Instructions

Set document protection. edit: trackedChanges/comments/readOnly/forms/none.

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": {
      "edit": "<edit>"
    },
    "name": "set_document_protection"
  }
}

Input Schema

NameRequiredDescriptionDefault
editYes
passwordNo
document_handleNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.4

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries full behavioral disclosure burden. It only lists possible edit values but fails to detail key behaviors: what 'protection' entails (e.g., preventing edits), whether existing protection is overridden, if the password parameter is required for certain modes, or any security implications. The output schema exists but is not referenced.

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 very short and front-loads the purpose, then lists the edit options. Every sentence is useful. However, it could be slightly more structured to separate purpose from parameter values.

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 has 3 parameters, 0% schema description, no annotations, and an output schema, the description is too sparse. It does not clarify the return value, the role of password, or how to remove protection. A more thorough description is needed for effective use.

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?

The description adds meaning for the 'edit' parameter by listing its allowed values, which is valuable since the schema has 0% description coverage. However, it does not explain the 'password' parameter (e.g., used to enforce or remove protection) or 'document_handle' (likely same as in other tools). The value list compensates partially for the schema gap.

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 tool sets document protection and lists the possible protection types (trackedChanges, comments, readOnly, forms, none). This specifies the verb and resource, distinguishing it from siblings like set_track_changes which deals with change tracking rather than protection.

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 offers no guidance on when to use this tool versus alternatives. It does not mention scenarios where document protection is appropriate, nor does it explain that this tool locks editing capabilities. Siblings include many other set_ tools, but no direct comparison is provided.

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