Skip to main content
Glama
Sign In
office-mcp-server

office-mcp-server

by jiahuidegit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

word_add_list

Add ordered or unordered list items to a Word document by specifying document ID and list content.

Instructions

添加有序/无序列表

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": {
      "docId": "<docId>",
      "items": "<items>"
    },
    "name": "word_add_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
docIdYes文档ID
itemsYes列表项
orderedNo是否有序列表

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

B3.3/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, and the description merely says 'add list' without disclosing behavioral traits such as whether the list is appended, the need for an existing document, or the effect of repeated calls. No additional behavioral context is provided beyond what annotations already convey.

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 short sentence that conveys the core purpose without redundancy. It is front-loaded and every word earns its place, exemplifying ideal conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with fully documented parameters and annotations, the description is minimally adequate. However, it omits context such as insertion point (e.g., at cursor vs. end of document) and the default behavior of the optional 'ordered' parameter, leaving some gaps for an agent to infer.

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 coverage is 100% with descriptions for docId, items, and ordered. The description mentions 'ordered/unordered', which aligns with the 'ordered' parameter, but it adds no significant meaning beyond the schema's own descriptions. Baseline 3 is appropriate due to complete schema documentation.

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 '添加有序/无序列表' (Add ordered/unordered list) clearly specifies the verb (add), resource (list), and its variants (ordered/unordered), distinguishing it from sibling tools such as word_add_paragraph and word_add_heading. The purpose is unmistakable.

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?

No guidance is provided on when to use this tool versus alternatives. The description simply states the action without any context about document prerequisites, list formatting, or exclusions relative to other word_add_* 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