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

office-mcp-server

by jiahuidegit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

excel_set_column_width

Idempotent

Set column widths in an Excel worksheet by specifying workbook ID, sheet name, and a column-to-width mapping (e.g., {'A': 20, 'B': 30}).

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": {
      "workbookId": "<workbookId>",
      "sheetName": "<sheetName>",
      "columns": "<columns>"
    },
    "name": "excel_set_column_width"
  }
}

Input Schema

NameRequiredDescriptionDefault
columnsYes列宽映射，如 { "A": 20, "B": 30 }
sheetNameYes工作表名称
workbookIdYes工作簿ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

C2.2/5.0
Behavior2/5

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

The description adds no behavioral details beyond the annotations. Annotations already indicate it is not read-only and is idempotent, but the description does not explain effects like overwriting existing widths, whether it applies to specific sheets, or potential side effects.

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

Conciseness2/5

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

The description is a single tautological phrase that restates the tool name. It is under-specified rather than concise, as it fails to provide any meaningful substance while occupying a line of text.

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?

With no output schema and sparse annotations, the description carries the burden of explaining the operation's behavior. It fails to describe what the tool actually does beyond setting column widths, leaving an agent unclear about the operation's scope, return values, or failure modes.

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 the schema already documents all three parameters. The description adds no additional parameter semantics, so a baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description '设置列宽' (set column width) essentially restates the tool name in Chinese, providing no additional specification or distinction from sibling tools. This is a tautology rather than a meaningful purpose statement.

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 gives no guidance on when to use this tool versus alternatives, no context about use cases, prerequisites, or exclusions. It does not mention how it relates to other excel tools or when it should be preferred.

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