Skip to main content
Glama
Sign In
WPS Office MCP

WPS Office MCP

by ZNaiGaomu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

wps_get_active_workbook

Read-onlyIdempotent

Retrieve information about the currently active WPS Spreadsheets workbook. Use this tool to inspect workbook details while keeping the document unchanged.

Instructions

获取当前打开的WPS表格工作簿信息

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wps_get_active_workbook"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-hardened.1

TDQS

A4/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, so the safety profile is covered. The description adds only the 'currently open' scoping and does not describe return shape or side effects, but for a simple getter this is acceptable.

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?

A single, front-loaded sentence with no filler. Every word earns its place.

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 parameterless getter with safety annotations, the description is largely complete. The only gap is that '信息' (information) is unspecified, but the tool name and context make the intent clear enough.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters and schema coverage is 100%, so there is nothing for the description to compensate for. Baseline 4 applies.

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 states a specific action ('获取' / get) and resource ('当前打开的WPS表格工作簿信息' / currently open WPS spreadsheet workbook info). This clearly distinguishes it from sibling tools targeting active documents or presentations, and from tools listing all open workbooks.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase '当前打开的' (currently open) implies this is for the active workbook, but the description gives no explicit guidance on when to prefer it over alternatives like wps_excel_get_open_workbooks or wps_get_active_document. Usage context is implied rather than stated.

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