Skip to main content
Glama
Sign In
WPS Office MCP

WPS Office MCP

by ZNaiGaomu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

wps_excel_get_formula

Read-onlyIdempotent

Retrieve the formula from a specific cell in an Excel worksheet. Provide the sheet name and cell address to get the formula used in that cell.

Instructions

获取Excel指定单元格的公式。

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>",
      "cell": "<cell>"
    },
    "name": "wps_excel_get_formula"
  }
}

Input Schema

NameRequiredDescriptionDefault
cellYes单元格地址，如 A1、B2
sheetYes工作表名称

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-hardened.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds no extra behavioral context (e.g., what happens if the cell has no formula, or whether it returns an error). With annotations present, the bar is lower, but the description contributes nothing beyond the bare function.

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, clear sentence with no redundant words. It is front-loaded with the core action and resource, achieving maximum conciseness.

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

Completeness4/5

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

For a simple read-only getter with two well-documented parameters and no output schema, the description is functionally complete. It tells the agent exactly what the tool does. The only minor gap is not describing the return format (e.g., returns a formula string), but this is not critical given the tool's simplicity.

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 both parameters (sheet and cell) described in the schema. The description does not add any additional parameter-level detail beyond what the schema provides, so the baseline of 3 is appropriate.

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 states a specific verb (获取/get) and resource (Excel cell formula), making the purpose unambiguous. It clearly distinguishes from sibling tools like wps_get_cell_value and wps_excel_get_cell_info by specifying 'formula'. However, it does not explicitly name alternatives, so it stops short of a 5.

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. It does not mention context, prerequisites, or scenarios where another tool would be more appropriate. The agent must 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