Skip to main content
Glama
dbett4

regulated-reporting-mcp

by dbett4

workiva_edit_table_structure

Adjust Workiva table structure by resizing, hiding, merging, or inserting/removing rows and columns.

Instructions

Edit table structure — resize, autofit, hide/unhide, merge, insert/delete rows/columns.

Args: table_id: The table UUID operation: One of: resizeColumns, resizeRows, autofitColumns, autofitRows, hideColumns, hideRows, unhideColumns, unhideRows, mergeCells, unmergeCells, insertColumns, insertRows, deleteColumns, deleteRows params: Operation-specific parameters including "revision". Examples: resizeColumns: {"revision": "...", "columns": [0, 1], "width": 120} hideColumns: {"revision": "...", "columns": [2, 3]} mergeCells: {"ranges": [{"startRowIndex": 0, "endRowIndex": 1, "startColumnIndex": 0, "endColumnIndex": 4}]} insertRows: {"revision": "...", "index": 5, "count": 2}

mergeCells/unmergeCells take a `ranges` LIST of half-open index objects
{startRowIndex, endRowIndex, startColumnIndex, endColumnIndex} (end-EXCLUSIVE:
the example above merges A1:D1). A singular `range` is auto-wrapped into `ranges`.
These ops are ASYNC — the endpoint returns 202 with `operationLocation` in the
body; poll that URL until status == "completed" to confirm the merge applied.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes
table_idYes
operationYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description carries the full transparency burden. It discloses crucial non-obvious behavior: merge/unmerge operations are asynchronous, return 202 with operationLocation, and require polling until status equals 'completed'. It also explains end-exclusive range semantics and singular range auto-wrapping, which are not visible in the schema.

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 front-loaded with a one-sentence summary, followed by a well-structured Args section, concrete examples, and a highlighted note about async behavior. Although lengthy, every segment adds necessary information for a multi-operation tool with free-form params; there is no filler.

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, 0% schema coverage, and absent annotations, the description covers the core semantics thoroughly: operations, params examples, range formatting, and async confirmation. It does not spell out exact parameter keys for every operation (e.g., autofit or delete), but the provided patterns and output schema make it sufficiently complete for confident invocation.

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

Parameters5/5

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

Schema description coverage is 0%, so the description is the only source of parameter meaning. It explains table_id, operation, and params, and provides concrete JSON examples for representative operations, clarifies the revision field, and specifies the exact format for ranges. This fully compensates for the empty schema.

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 opens with a specific verb and resource ('Edit table structure') followed by an explicit list of supported operations (resize, autofit, hide/unhide, merge, insert/delete rows/columns). This clearly delineates it from sibling tools like write_cells or format_cells, making the tool's scope unmistakable.

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

Usage Guidelines4/5

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

The description establishes clear context by enumerating the structural operations the tool performs, and the operation enum reinforces when to invoke it. It does not explicitly name alternatives or exclusions, so it falls short of a 5, but the intended use vs. cell-content tools is reasonably inferable.

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

Install Server

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/dbett4/regulated-reporting-mcp'

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