Skip to main content
Glama
Sign In
WPS Office MCP

WPS Office MCP

by ZNaiGaomu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

wps_get_cell_value

Read-onlyIdempotent

Retrieve the value of a specific cell from a WPS Spreadsheet by providing the sheet name, row number, and column number.

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": {
      "sheet": "<sheet>",
      "row": "<row>",
      "col": "<col>"
    },
    "name": "wps_get_cell_value"
  }
}

Input Schema

NameRequiredDescriptionDefault
colYes列号（从1开始）
rowYes行号（从1开始）
sheetYes工作表名称或索引

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-hardened.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds little beyond repeating the read operation, and it does not disclose behavior such as return format, empty-cell handling, or errors, but no contradiction exists.

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 a single short sentence that is front-loaded and free of filler. It could add sibling differentiation, but for what it contains it is appropriately concise.

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 read operation with fully documented parameters and strong safety annotations, the description is minimally adequate. However, it does not explain the relationship to wps_excel_get_cell_value, and without an output schema it also omits what value format the agent should expect.

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%, and each parameter (sheet, row, col) has a meaningful description in the schema, so the description does not need to add parameter details. It adds no extra semantics, matching the baseline for well-covered schemas.

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 (read) and resource (a specified cell's value), so an agent knows exactly what operation the tool performs. However, it does not differentiate this tool from the sibling wps_excel_get_cell_value, which appears to serve the same purpose.

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 provides no guidance on when to use this tool versus alternatives such as wps_excel_get_cell_value or wps_excel_read_range. There are no stated conditions, exclusions, or context for selection, leaving the agent to infer usage from the name alone.

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