Skip to main content
Glama

wps_et_create_pivot_table

Create a pivot table from a data range by specifying row, column, and value fields with aggregation functions like sum, count, or average. Automatically places the result in a new sheet if no destination sheet is given.

Instructions

基于数据区域创建数据透视表。row_fields/column_fields 为字段名(表头文字)数组,value_fields 为 [{field, func, name}],func: sum/count/average/max/min,name 为可选的自定义显示名。不传 dest_sheet 则自动新建工作表存放透视表。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dest_cellNo透视表左上角单元格,默认 A1
dest_sheetNo透视表放置的工作表名(可选,不传则新建)
row_fieldsYes行字段(表头文字)
table_nameNo透视表名称(可选)
source_rangeYes数据源区域,如 A1:D100(含表头行)
source_sheetNo数据源所在工作表名(可选,默认当前活动表)
value_fieldsNo值字段
column_fieldsNo列字段(表头文字,可选)
Install Server

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations provided, the description must disclose behavioral traits. It mentions that omitting dest_sheet causes automatic new sheet creation, and explains value_fields structure and allowed functions. However, it does not cover error handling, modification of existing data, permission requirements, or limits on data size.

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 paragraph of four sentences in Chinese, efficiently front-loaded with the primary action. It explains parameter structure without unnecessary elaboration, making it easy to scan.

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?

Given the tool's complexity (8 parameters, nested objects) and no output schema, the description adequately covers the core purpose, parameter structure, and default behavior. It omits return values and error handling, but for a creation tool with good schema coverage, it is sufficiently complete for an agent to use.

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 baseline is 3. The description adds value by clarifying that row_fields/column_fields are header text arrays and detailing the value_fields object structure (field, func, name) with allowed functions. This slightly exceeds the schema's individual descriptions but does not significantly compensate for the high coverage.

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 clearly states the tool creates a pivot table based on a data range. It specifies the key parameters (row_fields, column_fields, value_fields) and their structure, distinguishing it from sibling tools like wps_et_create_chart or wps_et_sort_range which serve different spreadsheet operations.

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 description implicitly defines the tool's purpose (creating pivot tables) but does not provide explicit guidance on when to use it versus alternatives, such as summarizing data with formulas or using other wps_et_* tools. No exclusions or alternative tools are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Antares422/draftly-wps'

If you have feedback or need assistance with the MCP directory API, please join our Discord server